Skip to content
NexFlow Automation

Process

Audit. Build. Handover. Measure.

One fixed-scope engagement model for every automation we deliver. Named deliverables at each stage, a fixed price you approve up front, and full ownership at the end.

  1. Automation Audit

    Cost
    Free call
    Output
    Roadmap + working POC

    We map your processes with the people who run them, quantify the manual work (hours per week, error frequency, response times), and rank automation candidates. It ends with a working proof-of-concept of one automation on your own process, so you evaluate evidence, not promises.

    Deliverables

    • Process map of the audited workflows
    • Prioritized automation roadmap (scope, outcome, effort per item)
    • Working proof-of-concept, demonstrated live
    • Honest no-go list: processes we recommend not automating, with reasons
  2. Scoped Build

    Cost
    Fixed price per deliverable
    Timeline
    Weeks, set in the spec

    One workflow or agent per deliverable, with defined inputs, outputs, and acceptance criteria you approve before we build. The spec doesn’t grow without a new agreement.

    Deliverables

    • Approved spec: inputs, outputs, acceptance criteria
    • Error handling, retries, and run logging built in
    • Demo against your real (or realistic) data before handover
  3. Handover

    Cost
    Included
    Owner
    You

    You own everything: workflows, prompts, integrations, credentials, and documentation written for a non-developer. If we disappeared tomorrow, nothing breaks.

    Deliverables

    • Full ownership transfer of workflows and credentials
    • Documentation your team can maintain without us
    • System diagram showing what talks to what
  4. Measure & Iterate

    Cost
    Maintenance optional
    Next
    Your call

    We track hours saved, errors removed, and response times against the audit baseline. From there you choose: the next automation, optional maintenance support, or nothing at all.

    Deliverables

    • Baseline vs. actual measurement of the agreed metrics
    • Optional maintenance support (never mandatory)
    • Candidate list for the next scoped build

Process artifacts

The checklist and the handover doc, published in full.

Agencies guard these as “methodology”. They’re just documents, and you should see exactly what you’re buying before you buy it.

audit-checklist.md

What we collect and ask during every audit.

  • Tool inventory: every SaaS system involved, who owns admin access, which have APIs
  • Process walkthroughs: sessions with the people who actually run the process, not their manager
  • Volume and frequency per process: items per day or week, peak periods
  • Error and rework rates: how often things go wrong, and the usual causes
  • Time accounting: who does the work today, and how many hours per week it takes
  • Exception patterns: every edge case and how it’s handled today
  • Access and security constraints: SSO, API keys, data-handling rules, anything off-limits
  • Success metric definitions: the baseline numbers we’ll re-measure after handover

handover-document.md

sample structure
  1. 01OverviewWhat the automation does, the business goal, and the acceptance criteria it was built against.
  2. 02Ownership & credentialsWhere every component lives, which accounts you own, and how to rotate keys. Nothing is registered in our name.
  3. 03Workflow mapDiagram of every trigger, step, and connection: what talks to what.
  4. 04Editing guideHow to change rules, thresholds, templates, and prompts safely, written for a non-developer.
  5. 05Failure modes & runbookWhat each alert means, how to retry, and how to run any step manually while something is broken.
  6. 06MonitoringWhere the run logs live and how to confirm the automation is healthy without reading code.
  7. 07AI configurationPrompts, models, provider data-sharing settings, and how to adjust guardrails and escalation thresholds.
  8. 08Change logEvery adjustment made during the build, with reasons, continued by your team after handover.

Honest limits

Some things shouldn’t be automated. We say so.

Part of the audit is disqualifying bad candidates. If a process lands on this list, we tell you not to buy. That’s the job.

  • Processes that require regulated judgment we can’t own (medical or legal decisions)
  • Processes that change every week and haven’t settled yet. Automating chaos just makes faster chaos.
  • Work that’s cheaper to leave manual than to specify, build, and maintain
  • Anything where a person must be accountable for the output by law or contract

Start with the audit. Keep the roadmap either way.

A 30-minute call about your actual processes. You leave with a prioritized automation roadmap, and the audit ends with a working proof-of-concept.

  • 30 minutes, on your real processes
  • Prioritized roadmap you keep either way
  • Working proof-of-concept before any contract
  • Reply within one business day