// How we work
Four weeks, then a build you can defend.
Two doors. A carrier that already knows what is broken brings us the scope. A carrier that wants the workflow mapped first runs Discovery. Either way, week one is instrumentation.
WEEK 01 / INPUTS
One workflow
You give us one workflow, two people for an hour each, system read access, and your change calendar.
WEEK 02 / PROCESS
Run the playbook
Instrument baseline, assess vendor surfaces, read governance gaps, rank development paths.
WEEK 03 / DELIVERABLE
Interactive demo
Instrumented baseline, surface evaluation, governance assessment, ranked build list with non-build reasons.
WEEK 04 / NEXT STEPS
Build planning
Build specifications are derived directly from discoveries. Never priced blindly.
// Engagement model
Two doors, and a step before either.
No commitment
Get a read on one workflow
One senior engineer, one workflow from a menu, one written assessment five business days after the session. It costs you sixty minutes with two of your people, your process documentation in whatever form it exists, and a sample of the real files. No inbox access needed.
Four weeks · fixed scope
Discovery
Fixed scope. An instrumented baseline, an integration-surface assessment, a governance-gap read, and a ranked build list including what we would not build.
Scoped from Discovery
Build
Senior engineers embedded with your team, building through sanctioned surfaces, with the transfer plan written into the first scope rather than sold to you later.
Understand your
business processes
like never before.
See how work actually moves between your teams — the real communication patterns, ticket flows, and documentation gaps that no org chart will ever show.
// Discovery
Four weeks, fixed scope, quoted before day one.
You give us
One workflow. Two people for sixty minutes each. Read access to the systems that touch it. Your change-control calendar.
We do
Instrument the current process. Assess the integration surfaces. Read the governance gap against your states. Rank the build list.
You get
An instrumented baseline of the target workflow, a surface assessment naming which builds are sanctioned, which need a partnership and which are not safe to build, a governance-gap read against your states, and a ranked build list — including what we would not build and why.
Not included
Any build. Any production change. Any commitment to a next engagement.
What follows
The build is scoped from it. The build is never priced publicly, because it is never the same twice.
Week one is instrumentation. If we cannot define your baseline in week one, that is the first finding — and it is usually the most valuable thing in the report.
// Build
Sanctioned surfaces, or we say so.
We build through the integration surfaces your core vendor supports — Guidewire Cloud API, Application Events, Integration Gateway and Cloud Data Access; Duck Creek’s gateway; ACORD AL3. Anything built against a non-sanctioned surface breaks on the vendor’s release schedule rather than yours.
If a build would require an unsanctioned surface — direct database reads, RPA, scraping — that is declared in the proposal and you decide, rather than being discovered at implementation. We verify general-availability status against the vendor’s own documentation before scoping, not after.
Do you have an ROI number?
We can show you what these systems did inside a carrier we ran. We cannot show you what they will do inside yours, and we will not model it before we have measured it. Before we build anything, we instrument your baseline.
Our own operating record is on Origins.
// What we bring
Not an empty repo, and not one model.
We don’t start from an empty repo. We arrive with a working library from ten years of running a carrier, and every build makes it better.
Nothing we build depends on one AI vendor. The rules, data handling and audit trail are deterministic code, and the AI sits behind a stable interface. When a better model ships, we swap it and the workflow stays put.
// Embed & transfer
Two things have to be true.
Partnership is not a tone. It is a set of preconditions — and two of them are about you. We are not the right firm for everyone, and the screen is short enough to run on a first call.
Truth number one:
You already buy engineering from outside.
Budget exists and a procurement path exists. Nobody in the room needs convincing that you would hire a firm to build software.
Truth number two:
You have engineers who can own what we build.
“You own what we build” is only true if there is a team on the other side to run and extend it. Otherwise we have built you a dependency, which is the thing we position against.
Four weeks, and you own the map.
Bring us the workflow you have already tried to fix.