Skip to main content
TKOSolutions

Build · Fix one workflow

One workflow, working in your systems in about 30 days.

I implement one qualifying workflow inside the tools you already use: where the work comes from, what state it is in, who owns the next step, what that step is, who approves anything customer-facing, and how you know it got better. You sign the acceptance scenarios in the first week, the fee is fixed, and you own what is built. Delivery is targeted for about 30 days from kickoff, subject to timely access and the agreed scope.

About 30 days

$9,999 founding price · from $14,999 standard

One principal · Scope agreed in writing

Who it’s for

When this is the right step.

For an owner, COO, or operations leader who can name the workflow that keeps breaking (new inquiries, client onboarding, quotes, renewals) and wants it fixed, not just diagnosed. Not sure which workflow yet? Start with the Blueprint.

  • You can name the workflow: inquiries wait for an owner, onboarding stalls between tools, or quotes and renewals depend on someone remembering.
  • A Blueprint, a diagnostic, or your own analysis already says what should change.
  • You want the fix working, not another report.
  • The work runs through one team and no more than three systems.

Outputs

What you get.

  • A workflow model: the states work moves through, what moves it, and who owns each step
  • Connection to up to two sources: a web form or webhook, a CSV or scheduled export, or one system with a documented API you authorize
  • Owner assignment and next-action rules, with overdue work surfaced in a daily view
  • A named-person approval before anything customer-facing is sent or any record is changed
  • An audit trail of what happened, including failures, visible to the people running it
  • A starting measure, a live measure, and a 30-day re-measure using the same definition
  • A handoff: runbook, two training sessions, and every account and credential in your name
  1. Days 1–5

    Model and agree

    Kickoff, access, and the starting measure. We agree the workflow model and you sign the acceptance scenarios.

  2. Days 6–21

    Build and pilot

    Sources, state, ownership, next actions, approval, and the audit trail, then a pilot with your team on authorized records.

  3. Days 22–30

    Accept and hand off

    Each scenario run in your environment, then training, the runbook, and ownership confirmed. The re-measure follows 30 days later.

Pricing

$9,999 for each of the first 3 paid Sprints at standard scope, then from $14,999. Fixed fee, stated on the written order.

The standard price rises only for named factors, each priced on the order before you sign: a second source that needs an API integration, more than five users, or a third system the workflow writes to. A prior Execution Gap Blueprint fee is credited once under its published terms.

How buying works

A request first. Payment only after fit is confirmed.

  1. 01RequestTell me about the workflow. Submitting the form does not charge you.
  2. 02QualifyWithin two business days I confirm whether it qualifies, or recommend the Blueprint, a Diagnostic, or another path.
  3. 03Written orderYou receive a written order with the scope, acceptance approach, start date, price, and payment schedule.
  4. 04KickoffI run one Sprint at a time, so the order states when yours begins. The 30 days start at kickoff.

What you provide

What I need from you.

  • One named workflow, and an owner on your side with about two hours a week during the Sprint.
  • Access to the sources and systems in scope within five business days of kickoff, held in your own accounts.
  • A named approver for anything customer-facing.
  • Data that shows the starting measure, such as an export of the last 90 days of the work.

Can’t name the workflow yet?

Start with the Execution Gap Blueprint. It finds the workflow worth fixing, and its fee is credited once toward a Sprint under its published terms.

See the Blueprint

Need procurement, security review, or several teams?

Larger programs do not fit a 30-day Sprint. We scope the right engagement directly.

Discuss an Enterprise Engagement

Boundaries

The fine print, up front.

Stated before any contract, so scope and expectations are clear.

  • One workflow in one business function, one team of up to five users, up to two sources, and no more than three systems.
  • Acceptance is five to eight written scenarios you sign by Day 5. The Sprint is accepted when they pass in your environment.
  • Changes after Day 10 go to a later Sprint, not into this one. If access arrives late, the date moves with it; the price does not.
  • Customer-facing actions stay human-approved. No autonomous sending, no CRM replacement or data migration, and no patient records, payment card data, or other regulated records.
  • You own the agreed code, configuration, and documentation. Subscriptions, hosting, messaging, and model usage are billed to your own accounts. No revenue, conversion, or response-rate result is promised.
  • Residential real-estate agents and teams: see BoundOS. Programs that need procurement, security review, or several teams are scoped as an enterprise engagement.

What comes next: After the 30-day re-measure, your team can run it, add Operate & Improve, or scope the next workflow as another Sprint. Each is a separate decision.

Typical work

What this usually involves.

Workflow state and ownershipSource integrationApproval and audit trailDaily action viewBefore-and-after measurement
What makes a workflow qualify?+

One workflow in one business function, with a clear trigger and a next step someone owns, running through no more than three systems and two sources of incoming work. You can grant access within five business days of kickoff, and no regulated records are needed. If it does not qualify, I will say so and suggest the Blueprint, a Diagnostic, or an enterprise engagement.

Is this a software product?+

No. It is a fixed-scope implementation that follows a repeatable method, first applied in RachelOS, a production system I designed and built for one independent real-estate business. What is built for you is configured to your workflow and owned by you.

Do we need a Blueprint first?+

Not if you can name the workflow and the systems. If you cannot yet, start with the Blueprint. Its fee is credited once toward a Sprint signed within 45 days of Blueprint delivery.

What if it takes longer than 30 days?+

The date assumes access within five business days and the agreed scope. Late access moves the date by the same amount, and changes after Day 10 become a later Sprint. Neither changes the price.

Will you use AI?+

Only where it helps and you approve it, for example a drafted message a named person reviews before it is sent. Many workflows need clear rules and ownership, not a model.

When do I pay, and what does “founding price” mean?+

After I confirm the workflow qualifies, you receive a written order with the payment schedule and an invoice. The first 3 paid Sprints are $9,999 for standard scope; after that, Sprints start at $14,999. The price on your written order is the price you pay.

One principal · Priced up front

Tell me what's stuck.

Name the workflow and the systems it runs through. I confirm within two business days whether it qualifies for a Sprint, and nothing is charged until you accept a written order.