Good reasons to talk
Repeated enquiry handoffs, client setup spread across tools, or documents that need a structured review. The work happens often enough to examine, and somebody can help define what a correct outcome looks like.
Services
Find the right fix. Build it carefully. Keep it useful.
I help you choose a practical improvement, put it into operation and decide what ongoing care it needs. Each stage has its own scope and deliverable. You do not need to commit to all three.
A good fit starts with a real recurring process.
The starting point is usually a U.S. B2B team of roughly 15–75 people, with an owner or operations lead who knows where work gets delayed. Team size is a guide; a clear process and a responsible owner matter more.
Work that needs a different scope
An undefined application, an open-ended AI experiment or an autonomous decision involving legal, financial, health or other sensitive consequences. These are not standard workflow builds. I will say when the fit is wrong.
01 · Decide
Workflow Audit
$2,000 fixed
A focused assessment of one end-to-end workflow across up to three systems. Two interviews, analysis and a readout turn a recurring frustration into a decision you can act on.
You receive a current-state map, baseline and data-quality notes, a check of existing software, ranked opportunities, cost assumptions and a scoped next step. A recommendation to use a native feature or make no build is a valid result.
The audit stands on its own. There is no obligation to buy a build and no automatic credit against later work.
02 · Implement
Focused Automation Build
$5,000–$20,000 planning budget
One agreed workflow, with a fixed written proposal after discovery. The price depends on the systems involved, the data, the exception paths and the amount of review and testing required.
Agree the behaviour
Define the start and end, ownership, data destinations, approvals and acceptance criteria. Spell out the cases that should stop or go to a person.
Build and test the paths
Connect the agreed systems and check ordinary inputs, duplicates, missing information and failures. Your process owner reviews the results before launch.
Hand over something usable
Include operating notes, an agreed configuration export, training and a clear list of dependencies. Confirm who will monitor the workflow and what to do if it stops.
n8n is my main build tool when it fits the job. Your existing software or a simpler rules-based integration may be the better choice. Tool selection follows the process; it is not the product you are buying.
03 · Maintain
Care & Improvement
From $1,000/month
Optional support for named workflows. The agreement defines monitoring, incident triage, a review cadence and a finite allowance for maintenance or improvements.
Before support starts, we agree the covered systems, business hours and time zone, initial-response target, escalation contacts and change allowance. An initial response means acknowledgment and triage, not a guaranteed fix within that window.
New workflows, major integrations, migrations, after-hours coverage and third-party subscription charges are outside the standard allowance unless explicitly included. If the ongoing cost is hard to justify, I will help define a lighter handover instead.
Know what you are buying—and what you need to provide.
My scope
The written proposal sets deliverables, testing, documentation, support boundaries and price. Changes are assessed and approved before extra work begins. I identify separate software and API charges before approval.
Your part
Name a process owner, provide suitable examples and arrange authorized access. Make the business decisions, confirm licences and data permissions, and provide feedback and approvals at the agreed points.
Ownership and exit
The agreement distinguishes your data and project work from existing components and third-party licences. Handover covers documentation, exports where available, account ownership and removal of access no longer needed.
Commercial details
All published prices are in USD. Taxes, payment milestones, cancellation, expenses and acceptance are set in the written agreement. The website does not take payment for consulting engagements.
A simple path from a question to working software.
Fit conversation
Discuss one process and decide whether an audit or another next step is useful.
Written scope
Agree the outcome, boundaries, responsibilities and cost before paid work starts.
Build, review and launch
Test the agreed paths with the process owner, resolve acceptance issues and confirm the launch plan.
Handover and optional care
Document the workflow, train the people using it and agree who looks after it next.
Scope questions, answered.
Can you work with our current software?
I check its native features, integration options and permissions first. Access or product limitations can affect scope. I will not promise a connection before checking the systems involved.
How long does a build take?
The proposal gives a schedule after the workflow, access and acceptance requirements are understood. A small handoff and a process involving several approvals do not need the same timetable.
Is the audit deducted from the build price?
No automatic credit is included. The audit is a separate deliverable you can use to make a decision or brief another implementation provider.
Can you provide 24/7 support?
That is not part of the advertised service. Any support agreement names real coverage hours, response targets and escalation steps. Hosting providers and software vendors remain responsible for their own services.
What if we need more changes?
Small changes can use an agreed care allowance. Work beyond it gets a separate estimate or scope, approved before it starts. There is no unlimited development promise.
Which handoff would you fix first?
A short conversation is enough to establish the process, its owner and whether a closer look makes sense.
Free 20-minute fit call.