How It Works
How we take one spreadsheet or tracker from the first conversation to a working system, with help as your team starts using it.
From the first conversation to a working system
We start with one spreadsheet, tracker or manual job that has become hard to manage. Together, we agree what a first working system needs to do.
Our Day-1 Build includes preparation before the focused build day and application care afterwards.
Agreeing the first version
We agree the part of the job we’ll replace, the information it needs and what your team should be able to do.
Work beyond that first version is discussed separately. Keeping the build focused makes it possible to get a working system into use quickly.
Before the build
A short call helps us understand what you’re using now and whether the work fits a Day-1 Build.
Before the build day, we agree the first version and check what needs preparing. That may include your data or a specific gap that needs resolving first.
This means understanding:
- What the work is used for
- Who relies on it
- What information needs to be captured
- What stages or statuses are needed
- What reports or views are needed immediately
- What can safely wait until later
We’ll say when a Day-1 Build doesn’t fit. A smaller fix, an existing product or a larger piece of work may be the better route.
The build day
By the end of the build day, the agreed first version is live and ready for your team to use.
Morning
We check the agreed job with you and confirm the steps, records and handovers the system needs to cover.
Midday
We build the working system using proven patterns and practical experience, shaped around how your team actually does the job.
Afternoon
We load your real data, test the main steps and check the important screens, actions and handovers with the information your team actually uses.
End of day
The system is live, and your team has a better place to run that part of the business.
What’s included
- One agreed first version, with preparation before the build day
- A simple data structure for that process
- Forms for adding and updating information
- Lists or views for seeing current work
- Real data import where practical
- Simple status tracking
- A live system and an agreed period of settling-in application care
What’s separate
- Complex automation
- Every historic report
- Multiple departments or unrelated areas of work
- Deep integrations with other systems
- Every edge case from years of spreadsheet use
- Large-scale data cleansing
- Care after the included period and work beyond the agreed first version
After your system goes live
During the first month, we help your team use the system and resolve any problems found.
That includes small adjustments needed for the job we agreed. Extra features, new areas of work and further development are discussed and priced separately.
We’ll explain what’s included and what happens after that period before the build.
What you’ll need to contribute
Your knowledge of the job helps us build the right system.
You’ll explain how the work happens, help check the information and confirm the main steps with us.
We’ll lead the build and the technical decisions. You don’t need to learn how to develop the software.
Let’s look at what you’re using now
Show us the spreadsheet or tracker and explain where it gets difficult. We’ll help you decide whether a focused build is the right next step.
Prefer to understand the cost first?
See what’s included and how pricing works