Values
What we hold to, and where we hold the line.
Four values run through every build. Each one comes with what it means day to day, and the point past which we will not compromise.
Operation first
We start inside your process. The software follows the way the portfolio runs day to day.
In practice
- Discovery begins on site, watching the current process before proposing a new one.
- The specification is written in the language of the operation, not the software.
- Screens are built around the decisions your team makes, not around generic entities.
Where we hold the line
We build a feature when it fits your operation. Common elsewhere is not a reason on its own.
Considered craft
Interfaces that stay calm at volume, with fewer screens and less training required.
In practice
- We review every screen for what can be removed, as well as what can be added.
- Design decisions are tested against a portfolio at real scale, not a handful of demo records.
- New staff can work the system within a day, without a manual.
Where we hold the line
We will not ship a screen that needs a training session to use. If it needs explaining, it gets redesigned.
Your data, your roadmap
We are a SaaS developer. We build and run your platform bespokely, you subscribe to it, and the data in it stays yours.
In practice
- The platform is built for your operation alone, never resold to another client.
- Pricing scales with your portfolio and your Modules, never with the number of people using it.
- You can export your data whenever you want, and we support you in doing it.
Where we hold the line
We build and maintain the software, and the data in it is yours to take with you.
In it long-term
We stay engaged after launch. The system keeps changing because the business keeps changing.
In practice
- Support and change requests are built into the subscription, rather than billed as a separate project each time.
- We review the platform against your operation on a regular basis, as well as when something breaks.
- The roadmap stays a live conversation with you, rather than a fixed document from the discovery phase.
Where we hold the line
We treat launch as the start. If your business changes and the software does not follow, we have not done the job.