Software development
Companies come to us at a specific point. The spreadsheet has forty tabs and one person who understands it. The off-the-shelf tool does 60% of the job and the other 40% happens in email. There is a database somebody built years ago that a whole department now depends on.
That’s what we get called in for. Very little of our work starts from nothing, and the constraints are usually the interesting part.
What clients ask for
Internal tools
Workflow, approvals, tracking, reporting. The screen your team lives in for six hours a day, which is why we care more about how fast it is to use than how it looks in a screenshot.
Web applications
Client portals, dashboards, onboarding and application flows, member areas.
Integrations
Getting two systems you already pay for to talk to each other, so the same figures stop being typed in twice.
Automation
The recurring manual steps in a process. Often a week of work that gives someone back an afternoon a month, permanently.
Taking over existing code
Someone built it, they’ve gone, it still runs the business and nobody wants to touch it.
How a project goes
Before we quote
We sit with the people who’ll use the thing. Not a requirements workshop with a whiteboard. We watch them do the work, because what people describe and what people do are rarely the same, and the gap is where the useful software hides.
Scope and price, in writing
What’s included and what isn’t. Fixed price where the work is well understood. Where it genuinely isn’t, a rate and a cap, and we’ll say which applies and why.
Two-week cycles
You see it running at the end of each one. Early versions will be rough and you should tell us so, because changing your mind in week three is cheap and changing it after launch isn’t.
Handover
The code, the documentation, the deployment setup and the access. Support afterwards is a separate arrangement rather than something you’re signed into by default.
Where we’re a bad fit
We’re a small team. If you need twenty people starting next week, that isn’t us. It also helps if the scope is settled internally before we start, because changing direction costs more once there is code to change.