Who this is for
- Operations teams running the business on spreadsheets, chat threads and copy-paste.
- Companies whose off-the-shelf ERP or CRM no longer fits how they work.
- Founders building a SaaS product who need a backend and a front end from one team.
Problems we solve
- Data lives in several spreadsheets and apps, and nobody has the full picture.
- The same information is typed twice, and reports are assembled by hand.
- There is no role-based access or history of who changed what.
- A generic product forces your team to work around it instead of with it.
What is included
- Discovery and workflow mapping with the people who do the work today.
- Data model, roles and permissions designed before screens are built.
- A web application on Next.js with a Django REST API behind it.
- Dashboards and reporting built from the data the system already collects.
- Integrations with the tools you keep, testing, deployment and documentation.
Not included
- Cleaning or re-keying historical data beyond the migration agreed in the plan.
- Licensing decisions for third-party software (we recommend, you decide).
- Round-the-clock on-call operations, unless included in a support plan.
What we need from you
- Access to the people who run the process today, for interviews and demos.
- Samples or exports of the data you work with (anonymised is fine).
- A decision-maker who can settle scope questions as they come up.
How the work runs
- 01Discover
We map the current workflow, the data behind it and the decisions people make, then agree on the first usable version.
- 02Design
Wireframes and a clickable prototype of the key screens, approved before development.
- 03Build
Two-week sprints, each ending in a demo of working software, with your feedback shaping the next sprint.
- 04Launch
Testing, deployment, roles set up for your team and a handover that explains how it all fits.
- 05Support
Monitoring, updates and new features on a plan sized to your business.
What you receive
- A workflow map and an agreed scope for the first usable version.
- Approved prototype of the core screens.
- The working product, delivered sprint by sprint with demos.
- Admin and role setup, API documentation and deployment.
- Handover documentation.
Proof and examples
We have not yet published case studies for this service. The product previews on the home page are illustrative concepts. Ask us to explain the proposed approach and what evidence is available for your particular scope before commissioning the work.
How we quote
- A written quote before any work starts. Custom work is quoted per phase after discovery.
- Changes are priced in writing before they cost anything.
- What shapes the quote: the number of user roles and screens, how much existing data has to be migrated, the integrations involved, and whether the product is internal or customer-facing.
Ownership and support
- Repositories, hosting accounts and domains are created in your name from day one.
- You receive documentation at handover: how the system is put together, how to deploy it and how to run it day to day.
- After launch you can choose a support plan for monitoring, updates and new features, or hand the project to your own team.
Questions about custom software
Should we build custom software or buy a product?
If a product exists that fits your workflow at a reasonable cost, we will say so during discovery. Custom software makes sense when the way you work is a real advantage, or when no product fits without painful workarounds.
Can we start small?
Yes. We agree on a first usable version, ship it, and grow it in two-week sprints based on what your team learns from using it.
Who owns the data and the code?
You do. The database, repositories, hosting and every account are in your name, and you receive documentation at handover.