Northwind Studio and Harbor & Rye are made up. Avery Chen is the designer. Rowan Hale runs the bakery. No invoice was sent, no DNS was read, and no payment link was created. The point is the order of work, and which workflow would fire if this studio used the packs as they are written.
The lead
Rowan submits the contact form on Northwind's own site. The body has a name, an email, a phone, and a sentence about a new menu and a launch before the holidays, plus the word budget.
Workflow R01, on a client site, or the free form template on a simpler setup, normalizes the email to lowercase and looks for the same address or the same submission id. This is the first post, so it appends a row, tells Slack, and drafts a thank-you. R07 scores it with rules only. The sample row is the fictional one in the lead-router assets. A model node stays off.
If Rowan double-clicks, the second post updates Submissions and Last Seen and does not Slack or score again.
The proposal
Avery sends a proposal. Workflow 09 starts its clock from the sent time, not from the draft. Day three is a short offer to walk through it. Rowan replies from the same address. Workflow 09a, if it is watching sent mail and the inbox, marks the lead replied so day seven does not go out. Avery does not add a discount in the follow-up.
They agree a deposit and a final. The project total and the schedule 50/50 go on the project row.
Kickoff and files
The deposit is recorded as paid through B01's checkout event. Because it is not the final milestone, B03 does not run. Workflow 02 can create the project. Workflow 13, or the free asset chaser, lists the logo, the menu copy, and a registrar invite. Nothing asks Rowan to paste a password.
A missing logo after a few business days becomes a draft. Avery reads it and sends it. The approval card is the idea of that pause, drawn as a plain card rather than as any chat product.
Launch
The pre-launch list is paperwork 06: a manual pass, one saved speed run with a target they actually agreed, forms, and the GA4 steps. Skill 09 is the same GA4 order with blank ids until Avery copies the real ones. After publish, workflow 18 fetches the homepage HTML and records a warn because a consent hint is missing. Avery fixes the banner, publishes again, and the next check can pass. 18 does not log into Google.
Before nameservers change, workflow 15 reads MX, SPF, DKIM, and DMARC and writes a report Avery can forward. In the sample, SPF and DMARC warn. Avery does not edit DNS from the workflow. Rowan sends a test from the bakery mailbox. The old mailbox stays until that message arrives.
Handover and the final invoice
B01 creates the final row and a Stripe payment link, not a hosted invoice. The email names the amount and the due date.
Rowan has not paid. Workflow 08 is about to send the handover. B03 sees the final row is not paid, sends the preview only, and stores a held gate. Originals are not shared.
The paperwork handover, document 07, is filled with registrar, auto-renew, the DNS inventory, and who pays the host. No passwords.
If the final sits past due, B02 sends one email per invoice: a note before the date, then day 1, day 7, and day 14, always the same link. Day 21 is a note for Avery to call, and the ladder stops.
When checkout completes, B01 marks the row paid and calls B03 with release. The originals folder is shared only because a folder id is present. If it were empty, the share would be skipped and the result would say so. Workflow 08 then sends the handover pack and, later, the testimonial ask.
The care plan
Harbor & Rye takes Growth: watching, a few hours that do not roll over, and a monthly report. M02 watches the URL. M04 reminds on domain and certificate dates and does not log into the registrar. M03, on the first, drafts a report for the previous month with incidents, hours, and a PageSpeed block labeled as scores only. Avery edits the draft before anyone else sees it.
What this story is not
It is not a claim about revenue, rankings, or a measured speed score. The canvases in assets/ are real editor screenshots from n8n 2.46.7. The emails, the report, the score row, and the checklist pages are rendered from fictional copy. Nothing in this file was produced by calling Stripe, Google, or a live DNS resolver.