Most companies run on a patchwork of SaaS tools: a CRM, a ticketing system, spreadsheets, a form builder, three automation services joined together with webhooks. At some point someone asks: "Would it be cheaper and better to build our own?" Here is how we help clients answer that honestly.
When SaaS is the right answer
Buy, don't build, when:
- the process is standard (email, accounting, payroll, video calls),
- a mature product fits at least 80% of your needs out of the box,
- the number of users is small, so per-seat pricing stays cheap,
- you don't have, and don't want, anyone to maintain software.
Don't rebuild Gmail or QuickBooks. That's money better spent elsewhere.
When custom tools win
1. Your process is your advantage
If the way you quote, schedule, inspect or approve is what makes you better than competitors, forcing it into a generic tool removes that advantage. A custom tool can encode your exact workflow.
2. Per-seat pricing is getting out of hand
Ten users at $50 each is easy to accept. Two hundred field staff at $50 each is $120,000 a year, every year. A custom tool has an upfront cost and modest hosting and maintenance, and it doesn't grow with headcount.
3. You're stitching too many tools together
When data moves through five apps and three automation services, every broken integration is a silent failure. One purpose-built tool with one database is easier to trust.
4. You need control over the data
Data residency, regulatory audits, or simply wanting to query your own data freely are common reasons to keep it in a system you own.
5. Manual work that's repeated every day
Copying data between systems, reformatting reports, checking documents by hand: these are ideal targets for Python automation and usually show the fastest return.
A simple cost comparison
| SaaS | Custom tool | |
|---|---|---|
| Upfront cost | Low | Medium to high |
| Ongoing cost | Grows with users | Hosting + maintenance, roughly flat |
| Fit to your process | You adapt to it | It adapts to you |
| Time to start | Days | Weeks |
| Data ownership | Vendor's platform | Yours |
A useful rule of thumb: add up three years of subscription costs plus the staff time lost to workarounds. If that's clearly more than the cost of building and running a focused tool, building is worth a serious look.
Keep the scope small
The biggest risk with custom software is trying to replace everything at once. The projects that succeed:
- start with one painful workflow,
- ship a working version in weeks, not months,
- integrate with the SaaS tools you keep (via their APIs) instead of replacing them all,
- grow based on what users actually ask for.
Why Python?
Python is our default for internal tools. It's fast to develop in, has a strong library for almost any integration (Excel, PDFs, email, APIs, databases) and Django gives you an admin interface, authentication and permissions almost for free. Many of our internal tools start as a Django admin with a few custom screens. That's enough for most back-office teams and costs a fraction of a fully custom UI.
Wondering whether a workflow is worth automating? Describe it to us and we'll give you an honest build-vs-buy opinion.