Social media for Software Development, sorted.
A month of posts written for your line of work: the caption, the hashtags, what to photograph and the day to post. Answer six questions and the first month is free.
Where your plan focuses
The platform and content mix SahiPost starts from for this trade. It is a starting point, not a rule.
Platforms
What you post
A sample post
This is the kind of post that lands in your plan, here for Instagram.
Myth: A fixed-price quote protects the client. Fact: A fixed price protects whoever wrote the scope most carefully. If the scope is vague, a fixed price does not remove the risk. It just moves the argument from the invoice to the change request, where it happens weekly instead of once. Specify tightly, or use time and materials with a capped budget. Both are honest. A vague fixed price is not.
Photo brief. Split card, developer-neutral. Red MYTH half, green FACT half, monospace type. No stock photographs of glowing code on screens.
Myths your customers believe
Posts that correct a myth earn trust. Your plan includes them, with your business name attached.
Myth. A fixed-price quote protects the client
Fact. A fixed price protects whoever wrote the scope most carefully. If the scope is vague, a fixed price simply moves the argument from the invoice to the change request.
Myth. More developers make a late project faster
Fact. Adding people to a late project means the people who know the system stop working to explain it. It gets slower first, and sometimes it never recovers.
Myth. Testing is what you do at the end if there is time
Fact. A bug found while the code is being written costs minutes. The same bug found after release costs a support conversation, a hotfix and someone's trust.
Myth. The client should not see it until it works
Fact. Long gaps without a working demo are where projects go wrong quietly. Something rough every two weeks beats something polished after six months.
How to write a brief a developer can estimate
- Describe what a user does, step by step, rather than listing features
- Say which parts are certain and which are still being explored
- Name the one thing the project fails without
Questions your customers ask
Who owns the source code?
You should, and it should be written into the contract. The repository sits in your organisation account with us granted access, so it is yours at every point rather than at handover.
Fixed price or time and materials?
Fixed price suits a tightly specified, unchanging scope. Anything exploratory works better on time and materials with a capped budget and a fortnightly review. We will say which one your project actually is.
How will I see progress?
A working demo every two weeks on a URL you can open yourself. Not a status document, not a percentage, something you can click.
Why do estimates change?
Because an estimate made before the unknowns are known is a guess with a confidence range. What should not change without discussion is the budget; estimates get revised at review points, in the open.
What happens to the project if you disappear?
You hold the repository, the cloud account and the domain, and there is a written handover document. If the answer to this question from any vendor is vague, that is the answer.
Do you provide support after launch?
Yes, as a separate agreement with a defined response time. Bundling indefinite support into a build price suits nobody, because it is either never used or endlessly argued about.
How do you handle change requests?
Written down with an estimate and a decision, before anyone starts. The problem is never that requirements change; it is that they change without anybody recording what it cost.
What do you need from us?
One decision-maker who can answer questions within a day. Projects stall on waiting for answers far more often than on engineering.
Hashtags to start with
Ready for a month of posts?
Six questions, about two minutes. No card, and the first month stays free.