Discovery and process mapping
We start by watching how the work is done today — the spreadsheets, the WhatsApp groups, the workarounds. The workarounds are the requirements; they are where the real process differs from the one written down.
Service
Custom Business Software
Operational systems built around how your business actually works — not around what an off-the-shelf product assumes.
What it covers
The work itself
System design and data modelling
The data model is the decision you cannot cheaply reverse. We design it first, in detail, and walk you through it in plain language before a line of application code is written.
Application build
Backend, database, admin interfaces, role-based access, reporting and the integrations that make it useful. Built in two-week increments you can see running.
Data migration
Getting your existing data in — cleaned, reconciled and verified — is a scoped part of the project, not something discovered in the final week.
Deployment and handover
Deployed to your cloud account, with infrastructure as code, documented runbooks, and a source repository you own from day one.
Support after go-live
The first month after launch is when the real requirements surface. We plan for that rather than treating it as out of scope.
Who it's for
And who it is not for
Businesses where the operational process is a genuine competitive difference, or is simply too specific for a product to fit. Typically 10–200 staff, running on spreadsheets or on software that has been bent past its limits.
Right fit if
- Your team maintains spreadsheets that the software should be doing
- You pay for a product and use 20% of it, badly
- Two systems hold the same data and disagree
- A process everyone knows is broken cannot be changed because "the system does it that way"
- Per-seat licensing has become a meaningful line item
- You need software to fit a regulatory or contractual process that is specific to you
Not the right fit if
- Problems that an off-the-shelf product solves well — we will tell you when that is the case
- Consumer mobile apps and design-led marketing sites
- Projects where the budget assumes offshore-commodity pricing
We would rather lose the project than take one we are the wrong firm for.
What you get
Deliverables, in writing
This list goes into the proposal. If something is not on it, it is not in scope — and we would rather argue about that now than in month three.
- Working software, deployed to your infrastructure
- Full source code in your repository, with no licence conditions
- Database schema, migrations and seed scripts
- API documentation where the system exposes one
- Deployment runbook and infrastructure as code
- Admin and end-user documentation
- Handover sessions with your team, recorded
Timeline & engagement
What it costs you in time
Typical timelines
Focused tool
4–6 weeksOne workflow, one or two user roles, limited integrations — a scheduling tool, an approval workflow, an internal portal.
Departmental system
8–14 weeksSeveral roles, real reporting, two or three integrations — the size most of our projects are.
Core operational platform
4–8 monthsMulti-module, multi-role, integrated with finance and third parties, replacing something business-critical.
Engagement models
Fixed scope, fixed price
A defined deliverable at a defined price, in milestones. Requires a discovery phase first, because a fixed price on an undefined scope is a fiction that ends badly for one of us.
Best for: Well-understood projects where the scope can genuinely be pinned down.
Discovery, then build
A paid discovery of one to three weeks producing a process map, a data model, a scope and a fixed quote. You can take that document to another vendor — it is yours.
Best for: Most projects. It is how we prefer to start.
Monthly retainer
A fixed monthly allocation of senior engineering, with priorities set at the start of each sprint.
Best for: Evolving products, or ongoing work after an initial build.
Related work
What this looks like when it is finished
Education
Coaching Center Management System
Fee defaulters, attendance and result cards in one place instead of five registers.
One system for enrollment, fee cycles, attendance, exams and parent communication — for academies that have outgrown registers and Excel.
Sales & Marketing
Custom CRM
A pipeline that matches your real sales process instead of the one your CRM assumes.
A sales pipeline shaped around how your team actually sells — for companies whose process does not fit a generic CRM, and who would rather own the code than rent the seats.
Other services
AI & Document Automation
AI applied to the boring, expensive parts of your operation — document extraction, classification and review workflows — with confidence scoring and a human in the loop.
Learn moreSystem Modernization
Legacy .NET applications and databases brought back under control — incrementally, without a rewrite that stops the business for a year.
Learn moreDedicated Team
Senior engineers embedded with your team, at your cadence — with the person who writes the code being the person you talk to.
Learn moreFAQ
Custom Software — questions we get asked
How do you price a project you have not built yet?
We do not, which is why discovery is a separate paid phase. One to three weeks produces a process map, a data model, a scoped build plan and a fixed quote. If you decide not to proceed, you keep the document — it is genuinely useful on its own, and you can take it to another vendor.
What if we need changes after the scope is fixed?
Changes are expected; pretending otherwise is what makes fixed-price projects adversarial. Small changes inside a sprint we absorb. Larger ones get quoted and you decide. What we do not do is agree to everything and then quietly compromise quality to absorb it.
Will we be able to maintain it without you?
That is the intent. Standard stack, conventional patterns, documented, in your repository. If you hire an in-house .NET developer in two years, they should be able to read the codebase and be productive in a week. We have no interest in being structurally impossible to replace.
Who owns the intellectual property?
You do, on payment. Source code, data model, documentation — all yours. Where we reuse a component we have built before, you receive a perpetual, unrestricted licence to it and we say clearly which parts those are.
Do you work with our existing developers?
Frequently, yes. We can build alongside an in-house team, take one module while they take another, or lead architecture while they build. The dedicated-team engagement is designed for exactly that.
Tell us what your operation actually does.
A 30-minute call, no slide deck. We will tell you whether this is worth building, whether an off-the-shelf product would serve you better, and roughly what it would take.
30 minutes · We reply within one business day.