How we work
From a free first conversation to software your team uses every day, in short steps you can see and steer.
- Home
- How we work
First, find the bottleneck
We sit with you and the people doing the work. Where do hours disappear? Which mistakes keep coming back? We list every friction point, from quoting to invoicing.
Then rank it and measure it
Biggest gain first, the 80/20 way. Before anything is built we agree today's figure and the target, so everyone knows what success looks like.
Build it with your team
Short releases your people use straight away, with a review every couple of weeks. If something new comes to light, we change direction rather than force the plan.
Run it, fix the next one
The system goes live, the numbers move, and you see your business clearly. Then we take the next bottleneck on the list, or you stop there. Your call.
| Bottleneck | Hours / week | Share |
|---|---|---|
| Re-keying orders | 14 | |
| Chasing job status | 9 | |
| Building quotes | 7 | |
| Month-end reports | 4 |
| Measure | Today | Target |
|---|---|---|
| Quote turnaround | 3 days | Same day |
| Orders re-keyed | All | None |
| Jobs shipped late | 1 in 6 | 1 in 20 |
| Release | What your team gets | Status |
|---|---|---|
| R1 | Orders in one place | Live |
| R2 | Job cards on the floor | Live |
| R3 | Quotes from templates | In review |
| R4 | Invoices to Xero | Next |
| Measure | Before | Target | Now |
|---|---|---|---|
| Quote turnaround | 3 days | Same day | Same day |
| Orders re-keyed | All | None | None |
| Late jobs | 1 in 6 | 1 in 20 | 1 in 14 |
A project, step by step
-
A free conversation
Over coffee in Shrewsbury, on your premises or on a call. We talk about your goals and what gets in the way. No obligation, no sales pitch.
-
Requirements and roadmap
If it looks like a good fit, we spend time with you and your team to understand how work really flows: where hours go, which mistakes repeat, what the data looks like. You get a written roadmap, ranked by value, with a fixed price for the first phase.
-
Build in short releases
We build the most valuable part first and release it to your team in small steps, with a review every couple of weeks. When something new comes to light, we adapt rather than force the original plan.
-
Go live, measure, improve
We train your team, switch over carefully, often running alongside the old way until everyone is confident, and measure against the targets we agreed at the start.
-
Support and the next bottleneck
Hosting, monitoring and improvements on a support plan. When you are ready, we take the next item on the roadmap. Or you stop there; it is your call.
a year spent copying, checking and chasing information by hand
What re-keying costs you
Move the sliders to match your business. The figures are your own estimate, worked out over a 46-week working year.
hours a year
full-time people, in effect
About the process
What happens in the first conversation?
We talk about your goals, what is slowing the business down and where time and money are being lost. It is free and there is no obligation. Most people leave with at least one idea they can use straight away.
Do we need a written specification?
No. Turning goals and frustrations into a clear, prioritised plan is part of our job. You bring the knowledge of your business; we bring the structure.
How is the work priced?
After the requirements and roadmap session, each phase gets a fixed price and a clear outcome before work starts. There are no open-ended day rates and no surprise invoices.
How involved does our team need to be?
Some involvement is essential and pays off: a few hours at the start to explain how things work, then short reviews every couple of weeks to try new releases and give feedback. We keep it light so it doesn't disrupt the business.
What if our requirements change mid-project?
They often do, because using early releases reveals better ideas. Short cycles mean we can change direction without waste. We agree any change in scope or price with you before acting on it.
How do you make sure the software is well built?
By following established engineering practice: proven, well-supported frameworks; all code in version control; automated tests on the parts your business relies on; secure coding, encrypted connections and regular security updates; and clear documentation. Every release is tested before it reaches your team, and your data is backed up. You own the code, and it is written so another competent developer could maintain it.
What support is there after go-live?
Hosting, monitoring, updates and improvements on a support plan, from the same person who built the system. Many clients keep adding modules over time.
What's slowing you down?
A free, no-obligation conversation with Evgeny, the person who would build it. Over coffee in Shrewsbury, on your shop floor or on a call. You will leave with at least one idea you can use, whether or not we work together.
Prefer email? [email protected]