Service 01
Custom software
Software that removes a specific cost. Usually that cost is a person retyping data, a spreadsheet that three people edit at once, or two systems that do not know about each other.
What we build
Internal tools
The thing your operations team currently does in a shared spreadsheet, with validation, an audit trail, and permissions that stop the wrong person changing a price.
Customer portals
A place for your clients to see their own orders, documents, status and history, so the answer stops arriving by email at eight in the morning.
Integrations
A reliable link between your ERP, CRM, accounting package, warehouse system or supplier feeds. Including the unglamorous part: retries, error reporting, and what happens when the other side is down.
Migrations
Moving years of records out of spreadsheets, Access databases or a system nobody supports any more, with the data reconciled against the source before anything is switched off.
Web applications
Customer-facing products where the interface is the product. Fast, accessible, and built so a non-developer can change the content.
Support after launch
Software that is used changes. A monthly arrangement covers fixes, small changes and the upgrades that keep dependencies current.
How a build runs
01
Process mapping
Week 1
We sit with the people who do the work now and write down what actually happens, including the exceptions they handle without thinking about them. Those exceptions are where fixed-price projects usually fail.
You getA written process map and a scoped first phase with a price.
02
First working release
Weeks 2 to 6
One job, done properly, running on your real data with a small group of real users. Not a prototype and not a demo. Something that can stay in production.
You getA deployed application, the repository, and the deployment pipeline.
03
Extend against use
Ongoing phases
Every phase after the first is shaped by what the first one taught us. Priorities come from the people using it, not from a roadmap written before anyone had touched it.
You getA scoped and priced phase, agreed before work starts.
04
Handover or maintenance
At any point
Documentation, a walkthrough for your own developers, and access to everything. Or a maintenance agreement if you would rather not carry it.
You getTechnical documentation and full ownership of every account.
When we are the wrong choice
- An off-the-shelf product already does this well. We will name the product.
- The requirement is a WordPress site with a contact form. That is a smaller job than we are set up for.
- You need a team to embed inside yours and take direction daily. We work on scoped outcomes.
- The deadline is next week and the scope is not written down.