We come to the work.
Some operations are too tangled to solve from a call. A Field Study puts Kevin onsite, watching the roles and workflows that actually matter, and turns what he finds into a Business Systems Roadmap you own.
- The roles that touch the work — who does what, and where it stalls.
- The real path a job takes from first request to done, including the paper and the texts.
- The systems in play — software, spreadsheets, inboxes — and the gaps between them.
- The handoffs where information gets re-entered, lost, or waited on.
- The reports leadership assembles by hand.
- A plain map of the current workflow, end to end.
- The specific points where time, tickets, approvals, or visibility are lost.
- Constraints that matter — access, integrations, compliance, busy seasons.
- The vocabulary your team actually uses, so the build fits.
Not a hundred ideas — a short, ranked list. Each opportunity is weighed on four plain questions:
- 01How much does it change daily operation?
- 02How much effort to build and adopt?
- 03What's the risk if we change it?
- 04How soon would you feel the difference?
RankedIllustrative example
3Quote follow-up trackerLater
1Shared dispatch boardNow
2Field photo → invoiceNext
4Replace the ERPNot now
A document you keep, whether or not you build with us.
- Current-state workflow map, in your language.
- Ranked opportunities with rough scope for each.
- A recommended first build — the honest place to start.
- What to leave alone: the systems already doing their job.
- Open questions and constraints, stated plainly.
Field Study
$5,000
+ approved travel
Credited in full toward a qualifying build.
You may not need this step.
If the work is straightforward and well understood, we'll say so and go straight from the Working Session to a focused build. The Field Study is for when the picture is genuinely tangled.
Questions? hello@ultramarlabs.io
Start with a Working Session.
We'll tell you whether a Field Study is worth it for your operation — or whether you can skip straight to building.