—Our process
Five steps, and the first three happen before you commit to a build. It is slower to start and considerably cheaper to finish.
Step 01
your business
We sit with the people doing the work and learn how orders, customers and information actually move — including the parts that live in someone’s head.
What happens
You end up with
A written summary of how your business runs today
Typically 3–5 days
Step 02
challenges
We separate the annoying from the expensive. Most businesses have a dozen problems and two that are genuinely costing money — those are the ones worth solving first.
What happens
You end up with
A prioritised list of opportunities with rough numbers
Typically 2–4 days
Step 03
solutions
You get options, not a single quote. What we would do first, what can wait, what you should not spend money on yet, and what it costs to leave things as they are.
What happens
You end up with
A recommendation document you own, obligation-free
Typically 3–5 days
Step 04
the solution
Delivery in short cycles with something usable at the end of each one. You see progress in a real environment rather than in a status report.
What happens
You end up with
Working software, documentation and training
Typically 4–16 weeks
Step 05
and improve
We stay on. Monitoring, updates and a monthly conversation about what the numbers are saying and what deserves attention next.
What happens
You end up with
An agreed service level and a named contact
Typically Ongoing
01Ground rules
These are the commitments that tend to matter most once a project is underway.
Every recommendation includes at least two paths, what each costs, and what happens if you do nothing. The cheapest option is always on the list.
A staging environment exists from week one. You see working software every two weeks, not screenshots in a status report.
Managers describe the process they think exists. The person doing it knows the one that actually does. We talk to both.
When something new comes up mid-project, you get the cost and the schedule impact before we start, not on the final invoice.
02Questions
If your question is not here, ask it directly — we answer these the same way on a call.
It is the normal starting point. Most conversations begin with a symptom — enquiries are slow, orders get missed — not a solution. Our first job is to work out what is actually costing you money, which sometimes turns out to be smaller and cheaper than expected.
No. The first call and the follow-up recommendation are free. If a project needs deeper investigation before anyone can quote responsibly, we propose a paid discovery phase and tell you the cost up front. You own the output either way.
Probably not. A number of our clients started with a single landing page. What matters is whether technology can make a measurable difference to your business right now — if it cannot, we will say so.
A landing page is one to two weeks. A five-page website is two to four. Catalog work is two to three weeks. Custom systems run eight to twenty weeks depending on scope. Every proposal includes dates, and we tell you early if one is at risk.
Expect a few hours in discovery, then roughly an hour every two weeks to review a working demo. Content is usually the bottleneck, so we help structure it and can write it if you prefer.
You do, on final payment — including source code, designs and content. Custom work is delivered to a repository you control. Catalog platform clients own their data and can export it in full at any time.
Get in touch
Tell us what is slowing the business down and we’ll come back with a recommendation — including the option of doing nothing yet.
We reply to every enquiry within one business day.
No pressure, just practical advice. If we are not the right fit we will say so and point you somewhere better.