Home / How we work
How we work

Six stages, and you can see progress at every one

Our process exists to remove the two things that kill software projects: unclear scope and invisible progress.

The process
01 Discover — We learn your process before proposing anything

Interviews with the people doing the work, a walk through the current system, and a written summary of what actually happens — including the workarounds.

02 Define — Scope, architecture and a costed plan

Functional scope, screens, integrations, data model and delivery milestones. You get a fixed quote or a team rate, with assumptions listed.

03 Design — Wireframes and a clickable prototype

We test the flow with real users before development starts, because changing a prototype costs hours and changing built software costs weeks.

04 Build — Two-week sprints, working demo at the end of each

You see progress every fortnight and can reprioritise. Code review, automated tests and CI are part of the sprint, not a later cleanup.

05 Test & deploy — UAT, migration rehearsal, then go-live

Your team signs off in a staging environment. Data migration is rehearsed twice. Go-live has a rollback plan and someone from our team on call.

06 Support & evolve — Warranty, then a support plan that fits

Documented handover, training for super-users, and an agreed response time for issues. Enhancements continue on a monthly retainer if you want them.

Deliverables

What lands in your inbox

Delivery is only transparent if it's written down. Here's the paperwork you can expect.

  • Weekly: a short status — done, in progress, blocked, and any decision we need from you.
  • Every sprint: a live demo on a staging link you can open yourself.
  • Every sprint: an updated backlog with priorities you can change.
  • At each milestone: a sign-off document listing exactly what was delivered.
  • At handover: source code, database scripts, deployment guide and admin documentation.
  • After launch: a support log with response and resolution times against the agreed SLA.
FAQ

Questions we get asked

How long does a typical project take?
A focused internal tool: 4–8 weeks. A departmental system: 3–5 months. A multi-module ERP rollout: 6–12 months, phased so the first module goes live early. We give a milestone plan before you commit.
What if the requirement changes mid-project?
Expected — it usually improves the result. Small changes get absorbed into sprint planning. Anything that moves the scope line gets a written estimate before we start, so nothing appears on an invoice unannounced.
Who owns the code?
You do, on final payment — source code, repositories and documentation. We don't hold clients through licensing.
Can you work with our in-house IT team?
Regularly. We can lead, co-develop or hand over progressively so your team takes ownership at the end. Knowledge transfer sessions are built into the plan.
What happens after go-live?
A warranty period covers defects at no charge. After that, most clients take a support plan with agreed response times and a monthly allowance for enhancements.
Do you sign NDAs?
Yes, before the first detailed discussion if you prefer. Client data stays inside environments you control.

Let's scope your project

Tell us what you're trying to fix. We'll come back with an approach, a timeline and an honest view of the cost — no charge for the first conversation.