Coming soon
A Cirql Works product

Describe a flow.
Watch it build itself.

A week of Patchworks clicks, collapsed into a sentence. Build. Script. Debug. Trace — all in chat, all against your live data.

Closed beta
Find out more
How it works

From SOW to shipped flow,
in one conversation.

Paste the Statement of Work into chat. PatchBuddy plans the project, verifies the environment, builds every flow and hands the keys back — all through the Patchworks API.

  1. 01
    Prompt

    Drop in the SOW.

    Paste the Statement of Work into chat, or upload the PDF the client sent. Plain English is fine — PatchBuddy reads it the way an engineer would.

    Chat input with a Statement of Work pasted in, a PDF upload chip and a Send SOW button.
  2. 02
    Plan

    Breaks the work down.

    PatchBuddy creates a Project, decomposes the SOW into Tasks, and lays out the order of operations. You see the plan before it touches anything.

    Project with four tasks listed: discovery, order flow, inventory flow, and review.
  3. 03
    Discovery

    Verifies the environment.

    Logs into Patchworks. Confirms access to every Connector, Endpoint and Data Pool the plan depends on. If something's missing, it stops and asks.

    Environment check showing connectors, endpoints and data pools all verified.
  4. 04
    Engineering

    Builds the flows, call by call.

    Every shape — connector, filter, mapping, dedupe, track step — posted through the Patchworks API. Custom payload scripts written and wired in as needed. Every call logged, every diff visible. The canvas updates live beside the log as each shape lands.

    Split view showing the API log on the left and the Patchworks canvas updating live on the right as each shape is posted.
  5. 05
    Review

    Hands the keys back.

    A clear summary of what was built, what was touched and what's ready to test. Approve and hand off, or send it back for revisions.

    Project summary with counts of flows, shapes and API calls, plus approve and request changes buttons.
All via the Patchworks API · Never off-platform.
Live learning loop

Less AI agent.
More virtual delivery employee.

PatchBuddy remembers. Every flow you approve, every pattern you correct, every client quirk you encode becomes part of your agency's shared knowledge base. Week one it's competent. Week twenty it works the way your senior engineers work — because that's who it's been learning from.

Client patterns

Acme uses kebab-case SKUs. Beta paginates at 250. Delta rejects weekend timestamps. PatchBuddy learns the quirks and applies them without asking twice.

Agency conventions

Your retry pattern. Your track-step naming. Your standard error alert. Your house style, applied by default on every new flow.

Engineer taste

Every approval, rewrite and rejection teaches. First drafts get sharper every sprint, until you're reviewing instead of writing.

Every correction teaches. Nothing ever needs re-explaining.