Test the change with your team.
You approve the change. We connect the tools and test the result.
We test expected results and failures. Your team keeps the code, tests and instructions.
We connect your tools and make AI systems for your team. You select the tasks and give approval for system changes. We do system tests and show the results.
Build. Test. Hand over.

You approve the change. We connect the tools and test the result.
We test expected results and failures. Your team keeps the code, tests and instructions.
Partnerships, projects, and Micah Johnson’s work history








Start with one workflow your team already knows. We connect its tools, make the rules explicit, and build around the decisions people need to keep.
Search connected tools for the records a task needs, with source links for review.
Bring scattered notes into a useful summary with evidence and open questions.
Turn an agreed handoff into a repeatable workflow across your existing systems.
Prepare a reply for a person to check before anything is sent.
Gather the checklist, source material and findings in one review workspace.
Preserve project decisions and provenance so the next task starts with context.
Test expected behavior and failure cases, then inspect what people actually use.
Deliver the code, checks and operating instructions your team needs to continue.
Connecting a tool should not mean handing over every action. We define what a workflow can read, prepare and change before it runs.
A draft can be automatic while a send waits for a person. The rules belong in the system, where your team can inspect and change them.
Your workflow permissions
Illustrative rules. Agreed for each workflow.
A submitter checks a template or app before sending it in. A reviewer can then inspect the version, its checks, and earlier feedback together. The Asset Dashboard gives the submitter a place to follow the review, make revisions, and manage the listing.
A template creator can check requirements in Designer with the Webflow Way Validator. App developers use Preflight and preparation guidance. The submission forms connect those checks to intake. On the reviewer’s side, review tools bring the queue, asset version, prior feedback, and evidence together. The reviewer decides what needs to change.
The Asset Dashboard brings progress and feedback back to the submitter, who can revise the asset and manage its listing. The film closes on the public Apps Marketplace, where people discover the published work.
Working code, checks and operating instructions should tell the same story. These extracts show the three together in our newsletter unsubscribe workflow.
UPDATE newsletter_subscribers
SET unsubscribed_at = datetime('now'),
active = 0,
status = 'unsubscribed'
WHERE email = ?
AND unsubscribe_token = ?
AND (unsubscribed_at IS NULL OR status = 'active')packages/canon/src/lib/newsletter/unsubscribe.ts
Newsletter unsubscribe: match the stored token before updating a record.
Extract from the shared server-side implementation.
The caller binds the email and token as parameters.
This is source evidence, not a live delivery claim.
const result = await processUnsubscribe(token, db);
expect(result.success).toBe(true);
expect(calls).toHaveLength(1);
expect(calls[0]!.sql).toContain('unsubscribe_token = ?');
expect(calls[0]!.sql).toContain('active = 0');
expect(calls[0]!.values).toEqual(['reader@example.com', token]);packages/canon/src/lib/newsletter/unsubscribe.test.ts
The matching regression test checks the query and its bound values.
Uses a database fixture to capture the query.
Checks that the stored token is part of the update condition.
A fixture test does not establish production database behavior.
Recheck eligibility immediately before dispatch.
If the selected audience no longer matches the approved
fingerprint, stop and prepare a new approval.
A subscriber's later opt-out takes precedence
over the send plan.docs/guides/NEWSLETTER_WORKFLOW.md
The operating guide connects an unsubscribe to the next sending decision.
Keep suppression in place when preparing an audience.
Treat a changed audience as a new approval decision.
Retain the evidence and recovery instructions for the operator.
You know the work and carry responsibility for the result. We build connections that keep that responsibility visible.
Agree on access, review and ownership before implementation. Keep the working code, the checks and the instructions when the build is handed over.
Map a workflowA named owner
Know who reviews the result and who can authorize the next step.
Rules you can inspect
Keep permissions and approval requirements in written, versioned artifacts.
Evidence you can trace
Follow findings back to their source instead of relying on a confident summary.
Your existing tools
Build around your systems and the access your team chooses to grant.
Clear action limits
Separate reading, drafting and changing records, with explicit gates for each.
Code you can maintain
Keep the agreed implementation and connection details with your team.
A useful history
Record what ran, what changed and where the outcome remains uncertain.
An operating handoff
Leave instructions for everyday use, recovery and the next responsible owner.
May–June 2026
Automation prepared usable evidence for 49 of 50 template submissions in the sample. Human reviewers made the decisions.
Read the field reportMicah Johnson contributed to this work as a Webflow employee and continues to work on template review at Webflow.

Cato Insights Hub
A publication hub built by CREATE SOMETHING with Webflow components.
Start with a mapping session. Bring one task and its owner. We discuss the problem, the work it needs, and whether we can help.
One problem or improvement
The person responsible
An existing workflow map, if you have one
Diagnosis and engineering needs
What your team needs to learn
A 30- or 60-minute opening
Discuss fit before paid work
Agree scope and checks before building
Review booking details before confirming