Should I build this myself or pay someone?Build it yourself, or pay someone.
5 minute read
Updated
The tools genuinely have got good enough that a determined non-technical owner can build something real in a weekend. That is not marketing, it is true, and it means the honest answer to this question is sometimes "do it yourself".
What follows is where that route works, where it stalls, and how to tell which side of the line you are on before you spend a month finding out.
When doing it yourself is the right call
If your project looks like this, build it yourself and keep your money:
- It answers questions from information you already have written down.
- It does not need to look anything up in a live system.
- Nobody is harmed if it is occasionally wrong.
- You, or somebody in the business, genuinely enjoys this kind of tinkering and will still be here in six months.
Where do-it-yourself projects stall
Almost every stalled project we hear about stalled in the same place, and it is not at the beginning. The first eighty percent goes quickly and feels great. The last twenty is where it sits.
- Connecting to live systems. Reading your calendar or your orders is where "configure a tool" turns into "handle authentication, failures, and the case where two systems disagree".
- The edge cases. The customer with two orders. The double booking. The person who asks something almost, but not quite, like the thing you prepared for.
- Knowing when to stop. Making it refuse to guess is harder than making it answer, and it matters far more.
- Maintenance. Something built in a burst of enthusiasm needs attention months later, usually when the person who built it is busy.
The cost that does not show up in the comparison
The do-it-yourself route looks free next to a quote, but it is not, and the difference is your own hours. If you spend three weekends and it works, that was probably a good trade. If you spend three weekends and it half works, you have paid the same price and still have the problem.
There is also a quieter cost. A half-finished system that answers customers badly is worse than no system, because it is now actively doing damage while you mean to get back to it.
Be honest about which of those you are likely to end up with, based on how the last project like this went.
The middle option people forget
It is not only build everything yourself or commission everything. You can have the difficult part built and keep the rest, and that is often the cheapest sensible answer.
The pattern that works: pay for the part that touches live systems and has to be right, then own and maintain the content yourself. We deliver with a walkthrough and a written guide for exactly this reason, so the arrangement does not depend on us permanently.
Side by side
Assuming a project that touches at least one live system.
| Built for you | Do it yourself | |
|---|---|---|
| Money out | A quote, known before you start | Tool subscriptions, which are much less |
| Your time | A few hours of answering questions | Substantial, and hard to predict |
| Live integrations | Included and tested | The usual place projects stop |
| Edge cases | Found in testing before launch | Found by customers after launch |
| When it breaks | Someone is responsible | You are, at the least convenient moment |
| Best suited to | Anything that must be right, or touches live data | Answering questions from what you already wrote |
How to decide in one question
Ask what happens if this thing is confidently wrong in front of a customer. If the answer is "we would laugh about it", build it yourself. If the answer involves a refund, a complaint, or a lost client, do not learn on that one.
And if you have already tried and it stalled, that is information rather than failure. The place it stalled is usually exactly the part worth paying for, and it is often a smaller job than starting over.
Still not sure which applies to you?
Fifteen minutes on a call is usually enough to settle it, and we will tell you if the answer is something we do not sell.
Book a callFAQ
Common follow-up questions.
Give your team its hours back.
A free 15-minute call. We look at where your week goes, show you what would take the most off it, and you see exactly what it costs before you decide.