Services / Three steps
We connect your systems and keep them running.
Right now your people carry the work between systems by hand. Three steps change that: a Workflow Sprint, then Implementation, then Management.
Before and after FieldProof
Before FieldProof
After FieldProof
After, a custom tool fills the gap and a person checks the work at every handoff. Yes, we build AI agents. Where they earn their keep.
Illustration, two rows lined up. Before: work moves from estimating through a spreadsheet, the PM platform, an AI tool and accounting, and between each pair small figures carry it by hand. It piles up at the spreadsheet handoff, while further down someone sits in a lawn chair waiting. After: the same row, but the spreadsheet's slot is an empty outline that two figures build into a new box labelled custom tool. Small bridges join every box, work flows straight through to accounting, and on each bridge a person checks each unit as it passes.
A set price to build it. A monthly fee to keep it running.
The Workflow Sprint and Implementation are each a fixed fee. Management is a monthly fee, and we earn it by keeping our fixes running.
Workflow Sprint
One workflow investigated, prototyped, and scoped for implementation.
We find the gap your people are carrying by hand and prototype the custom tool that fills it.
We map the workflow end to end, find where it breaks between systems, and build a working prototype on sample data from your own projects. You see what the fix looks like and what it's worth in hours before the full build starts.
We tell you which parts of the prototype work and which parts are simulated, so nobody mistakes a demo for the finished tool.
What you get
- A working prototype on your sample data
- A map of how the workflow runs today
- A scope for Implementation to build from
Implementation
The prototype becomes the tool your team runs every day.
We build the custom tool and the bridges that connect it to every system you run.
We build the real thing from the Sprint's scope and connect it to the systems you already run. We test it end to end, then your team tests it against the success measures we agreed on before the build. The people who'll use it get trained by role, on their own work.
We run the project. You get progress updates, one list of decisions, and scheduled reviews. Your people show up, test, and answer questions. When the workflow crosses into another company, like a sub's pay app rolling into the GC's, we set up the shared handoff and test it with both teams.
What you get
- The production build, connected to your systems
- Tested by your team before launch
- Training by role, with written procedures
See everything included
- The production build, connected to your systems
- Your data set up or moved over
- Acceptance testing: your team checks it against the agreed criteria before launch
- Training by role, recorded walkthroughs, and written procedures
- Permissions, security controls, and deployment documents your IT people signed off on
- A tested way to export your data
- A runbook, the written instructions for running it day to day
- A first results review against the baseline from the Sprint
Would rather run it yourselves?
Then Implementation ends with a handoff. Your team gets deployment instructions, the code and account access you agreed on, administrator training, and a supervised handoff before we step back. Choose it up front and it's part of the original Implementation.
Management
We keep it running, so nobody on your team inherits a new job.
We keep the custom tool and the bridges running, so the work keeps crossing and your people only step in to approve it.
Hosting, monitoring, maintenance, bug fixes, and defined support, for a monthly fee. When something breaks, there is a support channel, agreed response targets, and status updates until it is fixed.
You also see what it costs to run. Hosting and AI usage get reported, with spending alerts and an approval step before usage goes past what we agreed. We answer for it in month twelve the same as month one.
What you get
- Hosting, monitoring, and alerts
- Bug fixes and a support channel with agreed response targets
- Usage reports and spending alerts
See everything included
- Managed hosting, monitoring, and alerts
- Scheduled maintenance, plus security and dependency updates
- A support channel, incident triage, and agreed response targets
- Bug fixes within the supported scope
- Managed backups and scheduled recovery checks
- Usage reports and spending alerts
- Help for your team when they get stuck, and small configuration changes within an agreed allowance
Already built something?
Somebody on your team built a tool on a spreadsheet, a script, or ChatGPT, and it works until they're out. Start there instead of with a Sprint. We review it, connect it, harden it, and get the whole team on it, so it outlives the person who built it.
After we deploy
Once one workflow runs, we fix the next one, then the next. Same pattern. Prototype, Implement, Manage.
The next workflow
We prototype it in a Sprint, implement it, and add it to what we manage. It goes faster because the systems underneath are already connected.
Another integration or a bigger capability
Same flow. We prototype it, implement it, and add it to what we manage.
More people on it
Another division, office, or region. We prototype what changes for the new users, implement it with their access, data, and training, and roll it out in phases. Then we manage it with the rest.
When things change
A new process, a new platform, a reorganized team. We prototype the change, implement it, and keep managing it.
Questions about how it works
Do you sell software or get paid by software vendors?
No. We sell no software and take no kickbacks. The only thing we're selling is the fix. The systems that are working stay where they are, and when we suggest something new, the only reason is that it fits your workflow.
Do you only build software?
No. Most fixes mix technology with a change in how the work moves and some training for the people who do it. Sometimes plain automation or a cleaner process is the right fix, and we'll say so.
Do we have to start with a Workflow Sprint?
For a new fix, yes. The Sprint is where the prototype and the scope come from, and Implementation builds from that scope. If your team already built a tool that works, you can start with a review of that tool instead.
What happens when something breaks?
You report it through the support channel and we triage it against the response targets in your agreement. Bugs within the supported scope get fixed as part of Management. You get status updates until it's resolved.
What if we lose data or it goes down?
Management includes managed backups, written recovery procedures, and recovery checks on a schedule, so the way back is tested before you need it. If there is an incident, you hear from us while we work it.
Can our own team run it after launch?
Yes. Choose the handoff when you start Implementation and it ends with deployment instructions, code and account access, administrator training, and a supervised handoff. Otherwise Management keeps it running.
Is our data still ours?
Yes. Ownership, access, and export terms are in writing before the build starts. Implementation sets up the export and tests it, so you know the way out works.
Start with the workflow that's killing your team.
Tell us what it is, who does it, and which systems it moves between. We'll tell you straight whether a Sprint is the right first step and what the fix would take.
60 minutes.