Every adventure needs a great first mate.
Work with our crew of people and agents, led by Nav. We coordinate, cooperate and collaborate with you, and commit to results that matter. We improve one workflow with you and prove it. Then we set your business up with its own Nav and first mates.
Illustrative chart. Not for navigation.
Illustrative chart. Not for navigation.
Chart DM02 · Get Onboard · Edition 3 · October 2026
Your crew.
Read it like a map legend. Each symbol is a role, not a job title. In a team of one, you hold all three of yours. Only one role is in charge.
-
You The captain
Your business, your route, your call.
-
The people who do the work Your crew
They know where it sticks. Nothing changes without them.
-
Whoever holds the keys Tools and data
Keeps access and data safe. Signs off before anything goes live.
-
Our engineers Engineers
Design the workflow with you and sign off every proof.
-
Nav First mate
Keeps the route, the checks and the lessons. Navigates, never captains.
-
Specialist agents Crew
Research, drafting and analysis, inside clear limits.
The voyage, leg by leg.
Every good story has the same shape: a call, a guide, trials, a threshold crossed, and a return with something worth having. In this one, the hero is your business, and each leg leaves you something you keep.
-
Name the outcome The call
Start with what you’re good at. Then say where the work should end, and how you’d know it got there. Set what agents may and may not do.
- You bring
- whoever makes the call. In a team of one, that’s you.
- Pass when
- one outcome in one sentence, and someone who owns it.
- You keep
- a one-page brief.
-
Trace it back The chart
Start at the outcome. Follow the data and decisions back to where they begin. We draw it with the people who do the work.
- You bring
- the people who do the work, and access to the tools.
- Pass when
- the people who do the work recognise the picture.
- You keep
- a map of how the work really flows.
-
Find the friction Soundings
Mark where work waits, gets retyped, comes back, or sits with one person. Time it. Agree the target and when to stop.
- You bring
- a few weeks of real cases.
- Pass when
- the worst blockage named, with a baseline, a target and a stop rule in writing.
- You keep
- the scorecard.
-
Clear it alongside Sea trial
Clear the worst blockage on real cases, beside the old way. Customers see no change yet.
- You bring
- a safe place to test, and time to check the results.
- Pass when
- the work flows faster, without harm. If not, we stop and you keep what we learned.
- You keep
- evidence, or a cheap reason to stop.
-
Let it flow Casting off
Switch over with checks, a fallback and a tested way back. Agents earn more say only as the evidence comes in.
- You bring
- whoever holds the keys to your tools and data.
- Pass when
- checks tested, your people running it, the old way one step back.
- You keep
- a running workflow, and its runbook.
-
Keep it flowing Homecoming
Check the gauges each week until the target is met. Then your own Nav and first mates keep it flowing.
- You bring
- a short weekly check-in.
- Pass when
- the target met, you sign off, and the runbook works without us.
- You keep
- proven value, and a crew you can trust.
Discover, then write it down. Then evolve.
Between finding the friction and clearing it, we write one short record of how the work should run. Engineers would call it the drawings and the functional description. You and your people check it before anything is built.
- The outcome
- Who benefits, what counts as done, and what it’s worth.
- The map
- What the work touches (customers, jobs, invoices), where each one lives, and what crosses between your tools.
- The rules
- For every action: what starts it, what must be true first, who may do it, what needs a yes, and what happens if it fails or stops halfway.
- The proof
- Test cases, what actually happened, your sign-off, and what each finished job cost.
Pass when: someone who does the work and our engineer can each explain the normal case, an exception and an interrupted run, and agree on what proves each.
An example, chasing an unpaid invoice:
Starts when the invoice is overdue under your policy. First check it’s still unpaid, not disputed, going to the right person, and not already chased. Draft the reminder, get your yes, then send. Record that it was delivered. Sent is not paid. Disputed? Stop and hand it to you. Not sure it sent? Check before trying again.
Then it evolves. From the first trial run, every miss becomes a test the next run must pass. Only what keeps repeating becomes a shared tool for the next business. What’s particular to yours stays yours, written down where you can see it.
The needles we move.
Busy agents aren’t the goal. Flow is. We agree these numbers before we build. Each has an owner, a baseline and a target. If they don’t move, we stop or change.
-
Flow time
From start to outcome.
-
Wait share
How much of that time the work sits still.
-
Rework
How often it comes back.
-
Cost per outcome
What each finished job costs, people and machines.
-
Value
Net benefit, after every cost.
Where you are today The target you agree
- Daily
- Clear what’s stuck.
- Weekly
- Real work against the target. Keep going, change, or stop.
- Exit
- Value proven. You sign off. The runbook works without us.
Why we do this.
The boat matters. The technology matters. The process matters. The crew matters. But first: what are we playing the game for?
Our story starts in the 1990s, at a Kiwi engineering firm with a paperless office, far ahead of its time. The paper wasn’t the advantage. The operating system behind it was: codified know-how for bidding, designing and building factories. Above that sat the culture of the project teams, where people coordinated, cooperated and committed to the result. It is still the standard we work to.
Later, at WorldCom and BT, the work was routing and pricing algorithms. The same lesson kept returning: technology can optimise the game, but it can’t tell you which game is worth playing. Dreamineering exists to give any team, even a team of one, that operating system and that culture, with agents as crew, and people still choosing the game.
The goal: systems you can trust to turn an intention into an outcome. The rules of trust sit underneath, so each person gets an interface that fits how they think and act.
From The Setpoint, 2026.
Be the first proof.
We are our own first customers, and no outside result is published yet. When we take on your work, it’s one workflow, measured properly, nothing up front. When it’s proven, you choose: pay for the job, or partner with us and share in what comes next.
Got an itch to scratch? Drop Nav a line.