One handoff specification
The trigger, destination, required fields, routing rules, and owner for exceptions.
First workflow automation
Workflow automation. One handoff, connected.
We connect one repeated workflow across up to two supported systems. Requests reach the next owner with checked fields, duplicate protection, and a way to recover from failures.
From $3,500 USDOne-time project. Software and usage billed separately.
30 minutes with the co-founders. Check fit, tools and the next scoping step.
Start with one
recurring problem.
Someone copies the same details from one tool into another, checks them, and tells the next person to act. Start by automating that repeated handoff, including what happens when a request is incomplete or arrives twice.
Your first project, priced.
One connected workflow
From $3,500 USD
One-time project. Final scope and price agreed in writing.
Replace a repeated manual handoff with a working connection between the tools your team already uses.
Book a free scoping call ↗30 minutes with the co-founders to check fit, tools and the next scoping step. No obligation to proceed.
Included in the starter scope
- One trigger-to-handoff workflow across up to two systems with supported integration access.
- Agreed field mapping, routing rules, and a named owner for exceptions.
- A working flow with duplicate checks, failure handling, and a manual fallback.
- Tests using representative inputs, plus operating instructions and a handoff session.
- Quoted separately
- Additional workflows, major data cleanup, and custom connectors for systems without suitable interfaces are quoted separately.
- A larger project
- Quoted after scoping — Connect more systems, approval stages, branches, or teams around the same business process. This is an alternative scope, not an add-on to the starter price.
- Optional ongoing support
- Optional monitoring and fixes are quoted for agreed workflows, coverage, and limits; new workflows are separate projects.
- Timing
- We confirm the delivery schedule once integration access, rules, and test inputs are ready.
All prices are in USD. Third-party software, API usage, hosting and any telephony charges are separate. Support is optional; its coverage and limits are agreed separately. New workflows need a new scope.
From input
to a usable result.
Illustrative workflow. We agree the details for your project.
- 01 / The starting point
A purchase request arrives with a source identifier and the required details.
- 02 / The right context
Check the agreed fields and whether that request was already handled.
- 03 / Prepared for review
Prepare one approver task; hold incomplete or uncertain requests for review.
- 04 / A person decides
Retry a failed handoff without creating a second task, then record the outcome.
Tangible work
What your team receives
A working connection
One workflow across up to two supported systems, with field checks, duplicate protection, and a manual fallback.
Tests and operating instructions
Results for ordinary, incomplete, repeated, and failed requests, plus instructions for checking and recovering a stopped run.
Let’s check the fit.
Bring one task and your current tools. We’ll discuss the first step in a free 30-minute call.
From first call
to handoff.
- 01
Choose a handoff with a clear finish
Bring one normal input, one that gets stuck, and the destination record the next person needs. Confirm its business owner.
- 02
Write the exception rules
Define missing-field handling, repeated-input checks, retry limits, and which decisions need approval. Confirm the available integration access.
- 03
Review the pilot evidence
Compare the output and recovery behavior with the agreed criteria. Decide whether to revise the pilot or approve an operating routine.
What to agree
before we begin.
Not every process needs AI. Payment release, permission changes, and destructive updates are not silently included. Timing depends on actual integration access and process complexity.
How we evaluate the work ↗A few useful answers
Before we begin.
How much does a first project cost?
One connected workflow starts at $3,500 USD for the starter scope shown on this page. We confirm access, scope, exclusions, timing and a written price before work begins. Third-party software and usage charges are separate; ongoing support is optional.
What happens on the free scoping call?
In 30 minutes, we discuss one task, your current tools and the result you need. We check whether the starter fits and what is needed for a written proposal. If paid discovery is needed, we explain its scope and price first. You do not need a prepared brief or a paid assessment to book the call.
How will we judge whether the project is useful?
We agree a baseline and acceptance checks with the person who owns the work. Agreed sample requests reach the right destination; duplicates and failed runs follow the tested recovery rules. Where relevant, we also compare manual effort, correction work and operating costs. These checks guide the handoff; they are not a promise of revenue or savings.
Which handoff should we start with?
Choose a recurring transfer with a clear trigger, destination, and owner. A request becoming an assigned task is a useful example. Unclear or changing rules need to be resolved before building.
How are duplicates and retries handled?
We agree how each request is identified and how completed work is recognized. Tests cover repeated inputs and a failed connection, including cases where the destination may already have accepted the request.
Can we keep our tools?
We check their integration options and access first. The starter covers two systems with supported interfaces; custom connectors are separate.
How long does it take?
We set the schedule after checking the handoff, access, and exception rules. There is no blanket delivery deadline.
What happens after testing?
The owner reviews the results, recovery instructions, and held-work responsibilities before approving everyday use. Additional workflows are scoped separately.