Try it with the guide: SMB Pulse
SMB Pulse — a small business, run from one place
1. Pick your role
2. Pick a use case and follow its guide
Dana · owner
Start the day knowing the one thing that needs you and why, with every figure behind it traceable to its rows.
It opens as Dana, the owner.
0 of 5 steps done
Step 1. Open Workflows, then monday-brief, and press New run. The run appears at the top of the list as RUNNING and turns SUCCEEDED within a few minutes. It takes the pulse of every connected tool, gathers the week's meetings and deadlines, has the business-pulse agent write the brief, fills every figure from numbers already computed, and files the brief. Open the monday-brief workflow
Step 2. On the same screen, open Artifacts and choose filled_fields. Each row is one part of the brief, and every row reads
heldfalse.overall_lineopens with revenue month to date against the period before, and states the brief's as-of date.prioritynames the day's one priority and its reason.section.cashgives cash on hand, open receivables with the oldest overdue invoice, recent settlements and recent failed payments. Thetldrrows name a few of the failed payments, andsection.weekcounts the external meetings coming up. The wording changes from run to run; the figures do not. Open the monday-brief workflowStep 3. Open Operations, then pulse.overall, and press Call pulse.overall. Under ANSWERED,
statusis the business's colour (red, amber or green), andprioritygives its reason: typically one open invoice at risk of landing late, with its amount, due date and the email that warned about it. Inrisks, the invoice and the email each name the other inrelated_risk_ids. Call that customer about the invoice before payroll. Open pulse.overallStep 4. Open Operations, then pulse.section. In section, choose
cashand press Call pulse.section. Under ANSWERED, each figure carries its evidence and its grade:cash_availableopens the bank row behind it,receivables_ageingopens the oldest unpaid invoice,revenue_mtdnames the booked-revenue measure and the dates it covers, andfailed_transaction_amountopens the week's failed payments, largest first. Open pulse.sectionStep 5. Open Operations, then attention.list. In area, choose
cashand press Call attention.list. Under ANSWERED,itemslists what is waiting on you in cash: each chase-overdue run paused for your decision, with a link to it, and each connector that needs a refresh. Open attention.list
See whether the next payroll clears the tightest week, how far short of your cash buffer it leaves you, and which payments would close the gap.
It opens as Dana, the owner.
0 of 4 steps done
Step 1. Open Workflows, then plan-payroll, and press New run. The run appears at the top of the list as QUEUED and turns SUCCEEDED in under a minute. It checks payroll against your books, asks the cash advisor for the plan in plain words, and files it. Open the plan-payroll workflow
Step 2. On the same screen, open Artifacts and choose filled_fields. Three lines are the plan: the payroll date and amount with the low point of the tightest week, how far that falls short of your buffer, and the collections handed off. Each line reads
heldfalse; a held line was stopped because a figure could not be filled from the books. Open the plan-payroll workflowStep 3. Open Operations, then cash.payroll_gap, and press Call cash.payroll_gap. Under ANSWERED, read
verdict(covered,riskorgap),gap(how far short of the buffer you are) andcollections, which names each customer and invoice whose payment would close the gap. Open cash.payroll_gapStep 4. Open Operations, then cash.cash_outlook. Set horizon_days to 30 and press Call cash.cash_outlook. Under ANSWERED,
tightest_weekgives the week with the lowest balance and itslow_band_balance;recurring_costslists the bills the outlook counted, such as rent. Every figure has its rows inevidence. Open cash.cash_outlook
Chase every overdue customer once, in the tone their payment history calls for, without chasing anyone who has already paid.
It opens as Dana, the owner.
0 of 4 steps done
Step 1. The bookkeeper opens Operations, then cash.overdue_invoices, leaves min_days_overdue at
1and presses Call cash.overdue_invoices. Under ANSWERED,customersis ranked by what chasing each is worth, highest first. Each customer has apayer_score(good-payer,occasionally-lateorrepeat-late), atone(gentleorfirm), a total and its overdue invoices with days overdue. An invoice the payments already cover showspossibly_paidtrue, its settlement insettlement_evidence, anddraft_eligiblefalse. Long-overdue invoices showageing_statusred. Open cash.overdue_invoicesStep 2. Open Operations, then cash.cash_outlook. Leave horizon_days at 90 and press Call cash.cash_outlook. Under ANSWERED, look in
open_receivablesfor customers markedthin_historytrue: they have too little history to score, so they getoccasionally-lateby default. An invoice that is not overdue yet is not chased. Open cash.cash_outlookStep 3. Open Operations, then cash.draft_invoice_reminders. In customer_ids, type the id of each customer you want to chase, from the overdue list, pressing Enter after each. Press Run cash.draft_invoice_reminders. The run turns SUCCEEDED in under a minute. Under
drafts, each customer gets one reminder, in its own tone, covering all of its overdue invoices with their total and a pay-by date. The agent words each subject line, so it differs from run to run. Each draft is markedsimulatedtrue: nothing is sent and nothing is stored. Open cash.draft_invoice_remindersStep 4. Open Workflows, then approval-chase-overdue, and press New run. The run ranks the overdue customers and pauses at choose_who_to_chase. In the Runs tab, press Open decision. The table
chosen_candidateslists each overdue customer with aselectedtick. A possibly-paid invoice is excluded: its row hasselectablefalseand no tick, and itspayload_jsonholds both the invoice and the matching settlement. Untick every customer you do not want to chase and press Resume. The cash advisor drafts each reminder, the app fills its figures, and the run pauses again at approve_reminders. Press Open decision again. Read each reminder inapproved_reminders, edit itssubjectorbodyif needed, and tickheldfor any you do not want sent;approval_metaalready holds your sign-in and the time. Press Resume, which saves your edits first. The run turns SUCCEEDED, andsend_resultmarks each approved remindersimulated_sent. Open the approval-chase-overdue workflow
Understand how far revenue is down this month, against a fair comparison, and what is behind the difference.
It opens as Dana, the owner.
0 of 2 steps done
Step 1. Open Operations, then pulse.section. In section, choose
cashand press Call pulse.section. Under ANSWERED, read the section'sstatusand thenrevenue_mtd: revenue so far this month (value_money) against the same days of last month (delta_previous_money), the change (delta_value_money,delta_change_pct), itsdelta_directionand itsstatus, graded red when revenue sits well below the same days last month. Itsevidence_measuresname the measure and the dates it was read over, so the figure opens onto its rows. Open pulse.sectionStep 2. On the same answer, read
failed_transaction_amountandfailed_transaction_countfor the past week, each with itsstatus. The first entry offailed_transactions_namedis the one to follow up: the largest failed payment, with its transaction id,processor, amount, date and the payer's address. Smaller failed card payments follow it. Then read the settlements for the week against the week before: if they are up and green, the money that does arrive is arriving. Open pulse.section
See how the closed quarter went against the last one across the whole business, with any account the business relies on too much named as a risk.
It opens as Dana, the owner.
0 of 3 steps done
Step 1. Open Operations, then pulse.quarter_figures. In quarter, type the quarter that has just closed, in the form
YYYY-Qn, and press Call pulse.quarter_figures. Under ANSWERED,prior_quarterandyear_ago_quartername the two comparisons.revenue,margin,customers,complaintsandpipeline_next_quartereach set the quarter against the one before, and revenue also against a year earlier. Inconcentration, any customer above the share of wholesale revenue at which the app names a concentration is listed with itsshare_of_wholesale_revenue_pct,mean_days_late,payer_scoreand acustomer_signal, such as a competitor's move near that customer. Open pulse.quarter_figuresStep 2. Open Workflows, then quarterly-review, and press New run. The run appears at the top of the list as RUNNING and turns SUCCEEDED within a few minutes. It works out which quarter has just ended as of the books' date, takes that quarter's figures, has the business-pulse agent write the review with every figure as a placeholder, fills each placeholder from the figures already computed, and files the review as a brief. Open the quarterly-review workflow
Step 3. On the same run, open Artifacts and choose filled_fields. Each row is one part of the review, and every row reads
heldfalse.revenue_storysets the quarter's revenue against the quarter before.customer_storynames any concentrated customer, its share and how late it pays, and the signal near it. Theopportunityandriskrows give at most three of each.call_to_actioncloses the review. The wording changes from run to run; the figures do not. Open file_result for the review'sbrief_id, then open Operations, pulse.get_brief, paste it into brief_id and press Call pulse.get_brief: the stored review comes back unchanged, withkindquarterly_review. Open the quarterly-review workflow
Sign off the month the bookkeeper has closed out, approve the week's payment run before anything is paid, and share the month's close packet with the accountant.
It opens as Dana, the owner.
0 of 6 steps done
Step 1. Open Operations, then close.list_months, and press Call close.list_months. Under ANSWERED, find the month in
months. Itsstatusreadsready_for_sign_offwhen the bookkeeper has asked you to sign it off. Open close.list_monthsStep 2. Open Operations, then close.get_checklist. In month, type the month, as
YYYY-MM, and press Call close.get_checklist. Under ANSWERED, read each flag and what was decided about it before you sign. Open close.get_checklistStep 3. Open Operations, then close.sign_off, type the month in month and press Call close.sign_off. The month moves from ready for sign-off to closed, with who signed and when. Only the owner may sign; any other seat is refused by name. When the month is checked in a month-end-checks run, sign it off at that run's own pause instead: open the run, tick approved in sign_off_decision, press Save, then Resume, so the run can go on to release the accountant's packet. Open close.sign_off
Step 4. Open Operations, then bills.stage_run, and press Call bills.stage_run. The app plans the run and drafts one question: the cash sentence first, then the total, then the bills, labelled simulated: the owner executes in the bank. Only the owner may ask for it, and nothing is paid. Open bills.stage_run
Step 5. Open Workflows, then bills-payment-run, and press New run. The run stops at a pause on the oldest payment-run draft. Read the cash sentence and the total in approved_run, remove any bill you do not want paid, then press Resume to approve. The run records who approved, when and the bills left in. The app never adds a bill, and nothing pays itself: you pay in the bank. Open the bills-payment-run workflow
Step 6. Once the month's close packet is built, open Operations, then tax.share_with_accountant. In report_id, type the packet's report id, the
report_idthat close.build_packet returned (it startsrb-close-packet-), and press Call tax.share_with_accountant. Only the owner shares a report. Open tax.share_with_accountant
Find and decide every problem in the coming payroll run before it is paid, so the run you approve is right the first time.
It opens as Dana, the owner.
0 of 4 steps done
Step 1. Open Operations, then payroll.prepare, and press Call payroll.prepare. Under ANSWERED, read the pay period and pay date, and
people, one row per person paid.unknown_hoursholds a question for each shift with a clock-in and no clock-out, asking what time the person finished or whether the hours are to be left out.anomalieslists the missing clock-outs first and then the rest (unusual overtime, a rate change, hours with no hire record, leave beyond the balance), each with both numbers the rule compares.blockersexplains in plain English anything the payroll system cannot pay as it stands, such as a person paid by paper cheque, who fixes it and where. Nothing is corrected by this call. Open payroll.prepareStep 2. Open Operations, then payroll.word_flags, and press Add flags once for each flag. For each, type the person's name from the previous step in person, choose its kind in kind (
unknown_hoursorblocker), and paste the question or blocker text in detail. Press Run payroll.word_flags. The run turns SUCCEEDED in under a minute. Each flag comes back as one plain sentence that names the person and says what to do. The wording changes from run to run. The agent that wrote the sentence was given "Employee A", "Employee B" and so on, never a name or a pay figure; the app put the names back. Open payroll.word_flagsStep 3. Open Workflows, then payroll-prep, and press New run. The run lists every unknown-hours shift and every blocker, unknown hours first, and pauses at review_flags. Open Runs, then Open decision. In resolved_flags, untick keep to remove a flag. For a missing clock-out, set resolution to
stated_timesand enter clock_in and clock_out with the finish time the person gives you, or leave itacknowledgedto leave the hours out. Never enter a guessed time. Press Save, then Resume. Each kept flag is recorded as one decision, with who recorded it and when (the run's Artifacts, payroll_decisions). A stated finish time is recorded as a correction to submit; it is never added to any total. Open the payroll-prep workflowStep 4. On the same run, open Runs, then Open decision again. The next pause, stage_gate, is for the owner alone. It states the run sheet: gate_hours gives each person's hours, gate_totals the gross wages, the employer taxes, the cash going out (
cash_needed), the pay date and whether the run clears, labelledprojected, and gate_open_flags any flag still open. Press Resume, and the run is staged, labelled as simulated, for you to submit in the payroll system. The journal entry (gross wages and employer taxes) then waits at its own pause, journal_pause, confirmed against the staged run; resume it and the run completes. Open the payroll-prep workflow
Know what a second roaster costs each month, fully loaded, and whether the cash outlook carries it from the planned start date.
It opens as Dana, the owner.
0 of 3 steps done
Step 1. Open Operations, then hiring.afford_role. Type
Second roasterin role. Enter the pay range in hourly_low and hourly_high, each with its Currency, for example24.00and27.00USD; type the hours in weekly_hours, for example40; the start date in start_date, for example2026-11-01; and the monthly benefits in benefits_monthly, for example650.00USD. Press Add one_off_costs, typeHiring and equipmentin label, the amount in amount (for example1500.00) andUSDin its Currency. Leave basis attopand press Call hiring.afford_role. Under ANSWERED,rate_usedis the top of the range.base_monthlyis the monthly pay,employer_tax_monthlythe employer tax atemployer_tax_rate(labelledassumedwhen the business profile holds no rate), andbenefits_monthlythe benefits you entered.fully_loaded_monthlyadds them up. Inmonths, the start month also carries the one-off costs; every later month is the fully loaded figure. The answer'sscenario_idnames this scenario for the next steps. This call saves the scenario, its inputs and its figures, and nothing else. Open hiring.afford_roleStep 2. On the same answer, read
outlook, the business's cash outlook with the hire added from its start date.hire_outflowslists the one-off cost and the hire's payroll dates and amounts. The tightest week of the start month is shown twice, side by side:start_month_without_hireandstart_month_with_hire, each with its low-band balance, set against thecash_buffer.breach_introducedsays whether the hire pushes that week below the buffer. The nearest tight week is shownwithout_hireandwith_hiretoo, so you can see a shortfall that is there whatever you decide. Break-even givesbreak_even_revenue_monthlyat theblended_margin_pct, and how many units a month of the best seller the hire needs. Open hiring.afford_roleStep 3. Open Operations, then hiring.explain_affordability. Paste the
scenario_idfrom the first step into scenario_id and press Run hiring.explain_affordability. The run turns SUCCEEDED in under a minute. Under OK,verdict_sentencesays in one sentence whether the start month's tightest week stays above the buffer with the hire, with both low-band balances.considerationsholds exactly two things to consider, each built from the scenario's own figures, such as a tight week that is below the buffer whatever is decided, the fully loaded monthly cost with its one-off costs, or the revenue the hire must cover. The cash advisor chooses which two and points at the figures, and the app fills them, so the choice and the wording change from run to run and the figures do not.held_reasonisnull. Nothing is stored and nothing is sent. Open hiring.explain_affordability
Post the role with what success looks like, judge every applicant on the same criteria with their identity hidden, and answer every applicant.
It opens as Dana, the owner.
0 of 5 steps done
Step 1. Open Operations, then hiring.save_brief. Type
Second roasterin title. In duties, must_haves and competencies, type each item and press Enter: for example, dutiesRoast the House Blend and the seasonal batchandCheck every roast by cupping before it ships; must-havesTwo years of roasting experienceandFood-safety certificate; competenciesRoast consistencyandQuality checking. Type the hours in weekly_hours and the date in start_date, the same ones you priced (for example40and2026-11-01). Leave every pay field empty if no pay range has been set. Press Call hiring.save_brief. Under ANSWERED,brief_idnames the brief, andhas_pay_rangesays whether it carries one. A brief is never revised; a changed brief is saved as a new one. Open hiring.save_briefStep 2. Open Operations, then hiring.draft_job_post. Paste the
brief_idinto brief_id and press Run hiring.draft_job_post. When the run turns SUCCEEDED,statusisokanddocument.sectionsfollows the careers page's own headings in its own order.offered_sectionslists any standard section the page lacks, such as What success looks like: offered once, never added. A section you decline is listed in a new brief's declined_sections and is not offered again.pay_range_filledisfalsewhen the brief gives no pay range: no range is invented. The hiring writer words the post, so the wording changes from run to run. Open hiring.draft_job_postStep 3. Open Operations, then hiring.screen. Paste the
brief_idinto brief_id and press Run hiring.screen. The app reads every résumé sent to the jobs mailbox, removes each name, email address, phone number, address, photograph, school and date, and refuses the whole run if any identifying detail survives. When the run turns SUCCEEDED,applicantsholds one anonymised résumé per applicant, labelled Applicant A, Applicant B and so on;mappinggives each label's real name, for the owner only. Inresults, each applicant has abandcomputed by code from the criteria, and each criterion averdictwith the résumé sentence it rests on inquote, copied by code. A criterion the résumé does not mention readscannot_assess, with noquote: a missing fact, not a fail. A must-have that isnot_metbands the applicant no. Applicants identical in every relevant fact land in the same band. Open hiring.screenStep 4. Open Operations, then hiring.draft_candidate_replies. Press Add bands once for each applicant, and copy each
labelandbandfrom the screening; for an applicant with a criterion that cannot be assessed, type the fact to ask for in missing_fact, such asFood-safety certificate. Press Run hiring.draft_candidate_replies. When the run turns SUCCEEDED,draftsholds one reply per applicant, each with itsreply_kindset by code from the band: invite, hold (asking for the missing fact) or decline. The hiring writer saw only the labels; the app attached each real name and address afterwards.summarynames every recipient and the reply each gets. Nothing is stored and nothing is sent. Open hiring.draft_candidate_repliesStep 5. Open Workflows, then hiring-packet, and press New run. The run drafts the offer letter from the most recently saved brief and always pauses at review_offer. Open Runs, then Open decision. In reviewed_offer, one row per field, any field the brief cannot fill, such as
salary,candidate_nameorexpiry, is still a placeholder: no salary is invented. Fill in each value, edit anything that is wrong, press Save, then Resume. The run stages a simulated offer envelope, labelled as simulated e-signature, only when no field is still a placeholder. Resumed with a placeholder left, the run stages nothing and stops again at confirm, where the confirmed_offer table shows the letter once more with a needs column naming each blank: fill in each blank, press its Save, then Resume. Open the hiring-packet workflow
Have each contract read clause by clause, schedules included, see in plain words what to push back on, and export the redline once you have decided.
It opens as Dana, the owner.
0 of 4 steps done
Step 1. Open Operations, then contracts.upload. In file_ref, type the attachment's file name and press Run contracts.upload. The run turns SUCCEEDED. The app keeps the original, stores every numbered clause with its section and page, schedules and appendices included, and types the key terms it finds, each with the clause it came from. It proposes the contract's type and parties from the title and the opening, marked unconfirmed. A file that cannot be read is refused in plain words and nothing is stored. Repeat for each contract. Open contracts.upload
Step 2. Open Operations, then contracts.confirm_parties. In contract_id, type the filed contract's id. Check the proposed type and parties and type them in contract_type, our_party and counterparty, then press Call contracts.confirm_parties. Under ANSWERED, the contract's status is confirmed. Only the header changes; the clauses and terms are untouched. A contract that is not confirmed cannot be reviewed. Open contracts.confirm_parties
Step 3. Open Operations, then contracts.review. In contract_id, type the confirmed contract's id and press Run contracts.review. The run turns SUCCEEDED. The contract reader returns its findings, each with a severity, the problem, the market norm, the language to suggest and a playbook for asking, and each quote copied by the app from the stored clause. The business's other confirmed contracts are read alongside, so a term that reaches into another contract is named. The review ends with the app's own disclaimer that it is not legal advice. The reader words each finding, so the wording differs from run to run. Open contracts.review
Step 4. When you have decided what to ask for, open Operations, then contracts.export_redline. In review_id, type the review's id and press Run contracts.export_redline. The run turns SUCCEEDED and files two downloads under the run: the marked-up contract, with deleted words struck through and inserted words underlined, and a summary giving each finding's heading, clause and page, problem, market norm, suggested language and playbook, ending with the disclaimer. A review that suggests no change is refused and nothing is written. Nothing is sent to the other party. Open contracts.export_redline
Set the largest account's agreed payment terms beside how it actually pays, so you plan cash on the real payment time and know which clause to reopen at renewal.
It opens as Dana, the owner.
0 of 2 steps done
Step 1. Open Operations, then cash.overdue_invoices. Leave min_days_overdue empty and press Call cash.overdue_invoices. Under ANSWERED,
customerslists each customer with open invoices, largest first: how many are open, theirtotal,oldest_days_overdueand the invoice it comes from. Each has apayer_score, such asrepeat-late, read from its payment history in the books. Pick the largest account to check. Open cash.overdue_invoicesStep 2. Open Operations, then contracts.terms_vs_reality. In contract_id, type the id of that customer's filed agreement and press Call contracts.terms_vs_reality. Under ANSWERED, each row sets what was agreed, with the clause it comes from, beside what the books show, and states the gap. The actual figure comes from the books' own query, How many days does this customer actually take to pay, against the terms they are invoiced on?, which you can run yourself on Data; its
actual_dayscolumn gives the real time from invoice to cash. The answer ends with the app's fixed sentence "This is not legal advice." and offers no advice of its own. Nothing is sent or changed. Open contracts.terms_vs_reality
Rule out every grant the business cannot apply for, with the reason, before any time is spent, and start the eligible one from the funder's own checklist, with every missing figure marked rather than invented.
It opens as Dana, the owner.
0 of 6 steps done
Step 1. Open Operations, then grants.profile. Leave rebuild unticked and press Call grants.profile. Under ANSWERED,
sourceisstored: the profile was built once and is read as it stands.entity_typegives the kind of business, such asfor-profit, andmissingnames each kind of fact the business holds nothing for, such as registrations or certifications. Open grants.profileStep 2. Open Operations, then grants.screen. Press Add feed once for each opportunity and type what its notice says: its title, funder, eligible_entity_types and geography (type each value and press Enter) and deadline, for example
nonprofitand2026-11-30. Type today's date in as_of (for example2026-09-14) and press Call grants.screen. Under ANSWERED, the screen opens with a line noting the kind of business and runs anyway.excludednames each opportunity ruled out, with its reason, such as the wrong kind of business or a deadline that has passed. An opportunity the profile cannot settle, such as one limited to a place the profile does not name, is listed undercannot_tell, andeligibleholds only those that clearly fit. Open grants.screenStep 3. Open Workflows, then grant-response, and press New run. The run checks every sentence of the opportunity that says shall or must against the stored profile, as match, fails or unknown, and stops at go_no_go. A failed requirement would end the run here with the no and its reason recorded, before any drafting. In the Runs tab, press Open decision. Read
go_requirements, one row per requirement with itsmatch. Ingo_decision, leavedecisionatgoto continue; to decline, change it tonoand give your reason and your name indecided_by. Press Save, then Resume. A no is recorded with your reason, and nothing after it does any work. Open the grant-response workflowStep 4. Open Operations, then grants.compliance_matrix. In opportunity_id, type the eligible opportunity's id and press Call grants.compliance_matrix. Under ANSWERED,
rowsis the funder's checklist: one row per section, each with itsword_limitand itsweightin the score, then one row per form the funder requires. Open grants.compliance_matrixStep 5. Open Operations, then grants.draft. In opportunity_id, type the same id and press Run grants.draft. The run turns SUCCEEDED in about a minute. Under
sections, each section of the checklist is drafted in order, inside its word limit, andreadyistrue. Where the business holds no figure, the text carries a marked gap in square brackets, starting[GAP:, and each gap is listed again undergaps; no number is invented. The wording differs from run to run. Nothing is stored or sent. Open grants.draftStep 6. After a go, the grant-response run builds the checklist and the draft itself and stops again at review_submission. In the Runs tab, press Open decision. Read
compliance_matrixbesidegrant_submission. Fill every gap marked in square brackets ingrant_submission, check thatapproval_metanames you, press Save, then Resume. The run turns SUCCEEDED, andsubmission_resultrecords one simulated submission, labelled as simulated. A draft that still carries a gap, or one that is held, is refused by name and nothing is recorded. Nothing is sent to the funder. Open the grant-response workflow
Have the inbox sorted so only what needs you reaches you, with every handoff named, and a promise you made and have not kept in front of you.
It opens as Dana, the owner.
0 of 3 steps done
Step 1. Open Operations, then inbox.triage. In mailboxes, type each inbox to sort, for example
dana@,hello@andaccounts@, each followed by Enter, and press Call inbox.triage. Under ANSWERED,window_threadscounts every thread in the window: the last two days, plus those a person last wrote within two weeks. Each thread sits in exactly one place:needs_you,draftedorhandled, where handled covers newsletters, notifications, mail sent by the business and the threads handed off. Nothing is sent or changed. Open inbox.triageStep 2. On the same answer, read
needs_you, held threads first. A held thread shows why it is held, such as a lookalike sender domain on a request to change bank details, or a message that addresses the assistant directly, and each reads "verify by phone on the number already on file". Then readunkept_promise: the thread where you promised something, when you sent it, the date you promised by, and that nothing has been sent since, with a pointer to anything else open for that customer. Open inbox.triageStep 3. On the same answer,
handoffslists every thread handed to the work it belongs to, each with its line saying where it went, such as "Handed to Inbound — run Sort", "Handed to Bills — run Intake", "Handed to Contracts — run Upload" or "Handed to Cash — run Overdue invoices". A held thread that is also handed off stays inneeds_youtoo, markedalso_needs_you. Open inbox.triage
Go from a new organization with nothing connected to a first real answer from the business's own records, without being shown zeros that are not data.
It opens as Dana, the owner.
0 of 5 steps done
Step 1. Open Operations, then setup.onboarding_state, and press Call setup.onboarding_state. Under ANSWERED,
stepslists the setup steps with adoneflag each: Pick what hurts most, Connect your first tool, See your first result and Confirm your business profile.recommended_recipeis the Owner overview (pulse.overall), which reads whichever tool is connected. Open setup.onboarding_stateStep 2. Open Operations, then setup.list_tools, and press Call setup.list_tools. Under ANSWERED,
toolslists every tool the app can read, each with what it unlocks, stated before it is connected, and its status, such as connected, not connected orstale, with how fresh its data is.built_innames the public sources the app provides itself. Open setup.list_toolsStep 3. Open Operations, then setup.get_business_profile, and press Call setup.get_business_profile. Under ANSWERED,
thresholdslists every cutoff the app judges by, andcash_bufferis the one buffer the payroll verdict and the cash outlook both judge against. When nothing has been saved, the answer holds the shipped defaults. Open setup.get_business_profileStep 4. Open Operations, then setup.save_business_profile. Under thresholds, press Add thresholds and fill the cutoff's Name, for example
cash.receivables_ageing, with its direction, green, green_operator, yellow and yellow_operator; set cash_buffer and its Currency; and in headaches type each thing that hurts most, for examplemoney, and press Enter. Press Call setup.save_business_profile. The edit is written only when every threshold agrees with its declared direction; a rejected edit writes nothing, and the stored profile is unchanged. Open setup.save_business_profileStep 5. Open Operations, then pulse.overall, and press Call pulse.overall. Under ANSWERED,
statusis red, amber or green, andprioritygives the one thing that matters most, with its reason, such as an invoice from a customer who usually pays late that may not land by its due date.sources_textnames each tool the answer read and when it last synced, so a missing source is never hidden. Open pulse.overall
Luis · bookkeeper
Close the month from one checklist: see every line the month-end checks flagged, decide each one, and hand the month to the owner for sign-off.
It opens as Luis, the bookkeeper.
0 of 8 steps done
Step 1. Open Operations, then close.list_months, and press Call close.list_months. Under ANSWERED,
monthslists each month with itsstatus(open,ready_for_sign_offorclosed) andrun_count. Find the month you are closing: it should beopen, checked and waiting to be closed. Open close.list_monthsStep 2. Open Operations, then close.run_checks. In month, type the month you are closing, as
YYYY-MM. In processors_checked, typestripeand press Enter, thenpaypaland press Enter. Press Call close.run_checks. The checks match the month's payouts against its deposits and file what they find (payouts that do not match a deposit, uncategorised lines, duplicates, recurring charges, missing receipts, refunds without a credit memo, large month-over-month moves on an account and customer deposits not yet earned) as the month's flags. Nothing is written to the books. A closed month is refused until it is reopened. Open close.run_checksStep 3. Open Operations, then close.get_checklist. In month, type the same month and press Call close.get_checklist. Under ANSWERED,
statusisopenandflagsholds one row per problem.open_kindslists every kind still holding the month open, with how many of each, however long the checklist is. Each row has a kind inresult(for exampleuncategorised,duplicate,recurring,missing_receiptorrefund_without_credit_memo), the payee, aline_count, anamountand a note in plain words: an uncategorised payee says whether it has any history to suggest a category from, a duplicate pairs two charges of the same payee and amount a few days apart, and a regular charge is shown as recurring, not as a duplicate. A bill that was simply split is not flagged. Each row'sgroup_idis what the next step decides on. Running the checks again replaces the flags an earlier run left undecided, so each problem is listed once. A long checklist shows its first 200 rows: to see one kind's rows, type that kind in kind, and turn on open_only to leave out the flags already decided and the lines that agree. Open close.get_checklistStep 4. Decide the few flags that need judgment, one at a time: a duplicate charge, or an uncategorised payee whose note suggests a category. Open Operations, then close.resolve_flag. In month, type the month; in group_id, type that row's
group_idfrom the checklist; then press Call close.resolve_flag. The decision is recorded with who and when, and a change in QuickBooks action item is filed for you: the app itself changes nothing in the books. To leave one flag for later, use close.defer_flag with the same two fields instead: the deferral is recorded, and next month's checklist shows the flag again as already deferred, so it does not hold that month's sign-off. Open close.resolve_flagStep 5. Defer the rest in one action per kind. A month files many routine flags, such as small refunds still waiting for their credit memo (
refund_without_credit_memo) or receipts still being chased (missing_receipt), and every kind still open must be decided before the month can go for sign-off: a payout without its deposit (date_mismatch,missing_in_quickbooks,unmatched_deposit), an uncategorised payee you are leaving for later (uncategorised), aduplicateorrecurringcharge, an account that moved a lot on last month (variance) and a customer deposit not yet earned (unearned_deposit) included. Open Operations, then close.defer_flags_of_kind. In month, type the month; in kind, type a kind from the checklist'sopen_kinds; then press Call close.defer_flags_of_kind. Every flag of that kind that is still open is deferred at once, with who and when, under one change in QuickBooks action item; flags you already decided keep their decision. Under ANSWERED,memberssays how many it deferred andstill_openhow many flags are left. Repeat with the next kind inopen_kindsuntilstill_openis0. Open close.defer_flags_of_kindStep 6. Open Operations, then close.request_sign_off. In month, type the month and press Call close.request_sign_off. The month moves to ready_for_sign_off, with who asked and when. While any flag is neither resolved nor deferred, the app refuses and says how many are left. Open close.request_sign_off
Step 7. The owner opens Operations, then close.write_story, types the month in month and presses Run close.write_story. The cash advisor writes a short month story from the month's variance lines and the deposits not yet earned, and every figure in it is filled by code. The month must be ready for sign-off first; an open month is refused. Open close.write_story
Step 8. The owner opens Operations, then close.sign_off, types the month in month and presses Call close.sign_off. The month moves from ready for sign-off to closed, with who signed and when. Only the owner may sign; any other seat is refused by name. Open close.sign_off
Build the accountant's packet for a signed-off month (a workbook with the profit and loss, the reconciliation and the action items, and a one-page summary) and release it to her once you have read it.
It opens as Luis, the bookkeeper.
0 of 3 steps done
Step 1. Open Operations, then close.list_months, and press Call close.list_months. Under ANSWERED, find the month in
months. The packet is built only for a month whosestatusisclosed; if it still readsopen, the owner's sign-off comes first. Open close.list_monthsStep 2. Open Operations, then close.build_packet. In month, type the month, as
YYYY-MM. In story, paste the month story from the close, or leave it empty for a one-line statement of the month from the profit and loss. Press Run close.build_packet. The run builds a workbook (close-packet-YYYY-MM.xlsx) and a summary (close-packet-YYYY-MM-summary.pdf), keeps both, and files the packet as a report. A month that is not closed is refused. Open close.build_packetStep 3. Open Workflows, then month-end-checks, and open the month's run. Once the owner has signed the month off at the run's own sign-off pause (tick approved in sign_off_decision, press Save, then Resume), the run stops at its packet-release pause, release_packet. Read what it holds, tick release in packet_release, press Save, then Resume. The run builds the packet in its own step, build_packet_node, and files it for the accountant. The packet reaches her only when a person releases it. Open the month-end-checks workflow
Gather every bill that came by email or statement into one batch, each bill once, see which need your call and why, decide them, and have the supplier emails drafted for your approval.
It opens as Luis, the bookkeeper.
0 of 5 steps done
Step 1. Open Operations, then bills.intake, and press Run bills.intake with the fields left empty. The run gathers the messages carrying the accounts payable label, their attachments and the statement lines, dedupes them into bills and writes one batch. Nothing is coded, staged or paid. When the run has SUCCEEDED, its answer gives the
batch_idand how many bills fell in each bucket. Open bills.intakeStep 2. Open Operations, then bills.get_batch. In batch_id, type the batch id from the previous step and press Call bills.get_batch. Under ANSWERED,
needs_your_calllists the bills you must decide andcleanthe ones ready to go. Each bill shows its supplier,invoice_number,totaland itscopies: a bill that came as both a PDF and a statement line appears once, with both copies listed. A bill whose fields could not be read names them inunreadable, and leaves them empty rather than guessed. Undervendor_credits, each supplier with unused credit showsgross,credit,netand its ageingbucket. Open bills.get_batchStep 3. Open Operations, then bills.resolve. In batch_id, type the batch; in bill_id, type a bill from
needs_your_call; in decision, choose what you decided (set_code,split,accept_variance,not_duplicateorrule), fill code, amount or note as that decision needs, and press Call bills.resolve. The decision is stored once, with who decided and when. A bill that already has a decision is refused, and nothing is coded, staged or paid here. Read an unreadable total off the paper receipt; never guess it. Open bills.resolveStep 4. Open Operations, then bills.draft_vendor_emails. In batch_id, type the batch and press Call bills.draft_vendor_emails. Under ANSWERED,
emailsholds one draft per supplier per invoice that a supplier must answer, each addressed to the supplier's email on file with every figure filled by code, andheldlists any draft stopped because a figure was typed. Both lists are empty when no bill carries a question for a supplier. Nothing is sent. Open bills.draft_vendor_emailsStep 5. Open Workflows, then bills-vendor-emails, and press New run. The run drafts the supplier emails from the latest batch. When there is at least one draft, it stops at a pause for you to read, edit and release them; with no drafts, it ends without pausing. The send is simulated and labelled; nothing reaches a supplier until a person releases it. Open the bills-vendor-emails workflow
Stop a payment to a fraudster: find the email that asks to change a supplier's bank details, see that it is held and why, and verify it by phone before anything is paid.
It opens as Luis, the bookkeeper.
0 of 2 steps done
Step 1. Open Operations, then inbox.triage. In mailboxes, type
accounts@and press Enter, then press Call inbox.triage. Under ANSWERED, look at the rows inneeds_you. An email asking to change a supplier's bank details from a sender whose domain differs from the supplier's real one by a letter showsruleheld, with areasonthat names the lookalike sender domain and tells you to verify by phone on the number already on file. Do not reply to it and do not change any bank details. Open inbox.triageStep 2. The owner opens Operations, then inbox.triage, chooses
accounts@in mailboxes and presses Call inbox.triage. The same email is underneeds_you, held, and it is not listed underdrafted: no reply has been written for it. Call the supplier on the number already on file, never a number from the email, and keep paying to the bank details you already hold. Open inbox.triage
Run the week's payment run without missing payroll: order the bills the business owes, check what paying them leaves for the next payroll, keep the run to what cash allows, and hand it to the owner to approve.
It opens as Luis, the bookkeeper.
0 of 6 steps done
Step 1. Open Operations, then bills.plan_run, and press Call bills.plan_run with the fields left empty. Under ANSWERED,
proposalorders every open bill, most urgent first, each with its supplier, amount and due date.cash_sentencesays what balance is projected after this run, and whether the next payroll still clears or does not clear. Nothing is staged or drafted by this call. Open bills.plan_runStep 2. On the same screen, set as_of to today's date and press Add bills once for each bill due this week, filling bill_id, vendor, total, invoice_date and due_date from the books. Find them under Data, table qb_bills (press Browse, then filter it to the bills due this week);
txn_dateis the invoice date. Press Call bills.plan_run. Under ANSWERED,balance_after_rungives the projected balance for just these bills, andcash_sentencesays whether the next payroll still clears, and names any later payroll at risk whatever this run pays, with its gap. Open bills.plan_runStep 3. Open Operations, then cash.cash_outlook. Set horizon_days to 30 and press Call cash.cash_outlook. Under ANSWERED, read today's cash, the tightest week with its expected and low-case balance, and the
cash_bufferit is measured against.risk_sentencenames why that week is tight: the large bills and the payroll falling in it, and any customer payment that may land late. Open cash.cash_outlookStep 4. Open Operations, then bills.get_batch. In batch_id, type the latest batch id (from bills.intake) and press Call bills.get_batch. Under ANSWERED,
vendor_creditsshows each supplier's unused credit withgross,credit,netandbucket. The credit is shown, never netted silently, so you apply it when you pay that supplier. Open bills.get_batchStep 5. The owner opens Operations, then bills.stage_run, and presses Call bills.stage_run. The app plans the run and drafts one question: the cash sentence first, then the total, then the bills, labelled simulated: the owner executes in the bank. Only the owner may ask for it, and nothing is paid. Open bills.stage_run
Step 6. The owner opens Workflows, then bills-payment-run, and presses New run. The run stops at a pause on the oldest payment-run draft. Read the cash sentence and the total in approved_run, then press Resume to approve. The run records who approved, when and the bills left in. The app never adds a bill. Nothing pays itself: you pay in the bank. Open the bills-payment-run workflow
Marta · outside accountant
Well before the due date, have a worksheet for the quarter's estimated tax that is built from the books, net of payments already made, with every assumption and exclusion named.
It opens as Marta, the outside accountant.
0 of 4 steps done
Step 1. Build the worksheet. Type the year in year, such as
2026, leave quarter empty to read the latest completed quarter, and press Call tax.quarterly_estimate. This call only reads: it files nothing. Open tax.quarterly_estimateStep 2. Signed in as the owner, file the worksheet. Type the same year, leave quarter empty, and press Call tax.file_worksheet. The worksheet is filed under the default assumptions as the one copy everyone reads. Filing the same quarter again replaces it. The accountant reads what is filed but never files it. Open tax.file_worksheet
Step 3. Still as the owner, share it with the accountant. Type the filed worksheet's report id in report_id, such as
tw-q2-2026, and press Call tax.share_with_accountant. Only the owner shares a report. Open tax.share_with_accountantStep 4. Signed in as the accountant, export the packet. Type the
worksheet_idfrom the first step in worksheet_id, such asq2-2026, and press Run tax.export_packet. Wait for the run to turn SUCCEEDED. Open tax.export_packet
Months before the deadline, list every contractor who will need a 1099, from every payment source, with what each still needs and nothing on the list that does not belong there.
It opens as Marta, the outside accountant.
0 of 3 steps done
Step 1. Gather the list. Type the year in year, such as
2026, and press Call tax.contractor_list. This call only reads. Open tax.contractor_listStep 2. Signed in as the bookkeeper, draft the W-9 requests. Type the same year. In payee_ids, type the name of each payee whose W-9 is missing, as the list shows it, and press Enter after each. Press Run tax.draft_w9_requests and wait for SUCCEEDED. Nothing is stored and nothing is sent. Open tax.draft_w9_requests
Step 3. Approve the requests. Press New run. The run lists every payee with no W-9 on file and pauses at choose_payees. In Runs, press Open decision. In chosen_payees, tick selected for each payee to ask, press Save, then Resume. The run drafts one request per chosen payee and pauses at review_requests. The owner then presses Open decision, reads and edits each request in reviewed_requests, presses Save, then Resume. Open the tax-w9-requests workflow
Read the close packet the owner shared and check its profit and loss, reconciliation and action items in one pass.
It opens as Marta, the outside accountant.
0 of 4 steps done
Step 1. Open Reports. The packet is listed as the business's close packet, followed by the month, as
YYYY-MM. A packet whose name ends (superseded) was replaced when the month was rebuilt: open the one without that mark. Open ReportsStep 2. Read the packet's page from the top. It opens For your accountant's review., then The month gives the month's story, and P&L sets each account's figure this month beside the month before. Open Reports
Step 3. Under Variance lines, read each large change against the month before with its cause. Under Reconciliation, each payment processor's payout is set against the bank deposit, with both amounts and dates, the difference and its status. Open Reports
Step 4. Under Action items, read what the bookkeeper still has to change in the books, each with its amount and the action. When there is none, the packet says so. Open Reports
Mei · wholesale sales rep
Start the morning knowing whom to call first and why, with no current customer on the list and the first call already prepared.
It opens as Mei, the wholesale sales rep.
0 of 2 steps done
Step 1. Rank the leads. Leave count and rep empty and press Call sales.call_list. Open sales.call_list
Step 2. Prepare the first call. In contact_ids, type the contact id of the first lead on the call list and press Enter. Press Run sales.draft_call_prep and wait for SUCCEEDED. Nothing is booked or sent. Open sales.draft_call_prep
Know every Friday whether the pipeline covers the month's new-business target, which deals have slipped or gone quiet, and which have no next step.
It opens as Mei, the wholesale sales rep.
0 of 3 steps done
Step 1. Check coverage. Leave as_of empty and press Call sales.pipeline_health. Read
coverageandstages. Open sales.pipeline_healthStep 2. Find the slipped and stale deals. On the same answer, read
deals_needing_attention. Nothing is moved from here: change a date or a stage in the CRM yourself. Open sales.pipeline_healthStep 3. Queue the next steps. On the same answer, read
missing_field_deals, and give each deal a next step in the CRM, starting at the top. Open sales.pipeline_health
Have every gap in the CRM named with a proposed fix and its evidence, so that keeping the records accurate is a yes or a no for each fix, never an afternoon of typing.
It opens as Mei, the wholesale sales rep.
0 of 3 steps done
Step 1. Find the gaps. Leave as_of empty and press Call sales.pipeline_health. Read
duplicate_contacts, thenmissing_field_dealsandmissing_field_contacts. Open sales.pipeline_healthStep 2. Get fixes proposed. In deal_ids, type the id of each deal you want fixed, from
missing_field_deals, pressing Enter after each. In duplicate_set_ids, type the id of each duplicate set to review and press Enter. Press Run sales.propose_crm_fixes and wait for SUCCEEDED. Nothing is written to the CRM. Open sales.propose_crm_fixesStep 3. Decide each fix. Press New run. The run scans the pipeline, asks the sales coach for a fix for each gap, and stops at review_proposals. In the Runs tab, press Open decision. Untick every fix you reject, and leave every
flag_onlyrow unticked, because ticking one refuses the whole resume. Press Save, then Resume. Open the crm-cleanup workflow
Answer the inquiry that cannot wait before the sender looks elsewhere, refer what the business does not sell, and never let the text of an inquiry make the business promise anything.
It opens as Mei, the wholesale sales rep.
0 of 3 steps done
Step 1. Sort the inquiries. Press Call inbound.sort. The first call reads the week before the as-of date; each later call returns only what has arrived since the one before. Open inbound.sort
Step 2. Draft the replies. Press New run. The run sorts the new inquiries, the sales coach drafts a short reply to each one that may be answered, and the run stops at review_drafts. In the Runs tab, press Open decision. Nothing is sent yet. Open the speed-to-lead workflow
Step 3. Approve the replies. On the same decision, read each reply and edit its
bodyif needed. Tickheldfor any reply you do not want sent. Press Save under each table, then Resume. Open the speed-to-lead workflow
Know which new accounts to approach next, each with a current and sourced reason to call, without letting prospects inflate the pipeline.
It opens as Mei, the wholesale sales rep.
0 of 5 steps done
Step 1. See the ideal customer the app derives. Press Call prospecting.derive_icp. This is a proposal only: nothing is saved. Open prospecting.derive_icp
Step 2. Signed in as the owner, save it. Fill icp from the proposal, correcting any part the business knows better, and set service_area. Press Call setup.save_business_profile. The profile is written only when every part passes its checks. Only the owner saves the ideal customer. Open setup.save_business_profile
Step 3. Rank the prospects. Press Call prospecting.build_list. Open prospecting.build_list
Step 4. Write the reasons. Press Run prospecting.write_reasons and wait for SUCCEEDED. Open prospecting.write_reasons
Step 5. Approve each gate. Press New run. The run ranks the prospects, keeps those with a person to write to, writes each reason, and stops four times. In the Runs tab, press Open decision at each pause in turn. At list_pause, tick
selectedinchosen_prospectsfor each prospect to write to. At copy_pause, tickapprovedinreviewed_copyfor each sequence you accept. At send_pause, tickapprovedinapproved_sendsfor each first message to send. At crm_pause, tickapprovedinapproved_crmfor each prospect to record. After each, press Save, then Resume. Open the grow-pipeline workflow
Reach the customers who have stopped ordering while they can still be won back, with the reason in view, and never send a sales message to someone who is complaining.
It opens as Mei, the wholesale sales rep.
0 of 3 steps done
Step 1. Find who drifted. Press Call winback.find_quiet. Open winback.find_quiet
Step 2. Draft a sequence. In customer_id, type a customer's name as the list shows it, leave offer empty, and press Run winback.draft. Try one customer marked
calland one that is onlyquiet. Nothing is stored or sent. Open winback.draftStep 3. Approve the sequences. Press New run. The run lists the quiet and gone customers and stops at select_customers. In the Runs tab, press Open decision, untick every customer you do not want to write to, then press Save and Resume. At review_drafts, press Open decision again, read and edit each message, type each customer's offer in
confirmed_offers, then press Save and Resume. Open the reactivate workflow
Send a prospect a proposal the same day they ask for prices, priced from what comparable accounts already pay and clear about what it does not cover.
It opens as Mei, the wholesale sales rep.
0 of 3 steps done
Step 1. Gather the comparables. In deal_id, type the prospect's deal id, such as
planted-deal-0. In requested_lines, type each line the prospect asked about, pressing Enter after each. Press Call proposals.gather. Open proposals.gatherStep 2. Draft the proposal. Fill deal_id and requested_lines as in the step before and press Run proposals.draft. Wait for SUCCEEDED. Nothing is stored or sent. Open proposals.draft
Step 3. Signed in as the owner, approve it. Press New run. The run drafts the proposal and stops at review_draft. In the Runs tab, press Open decision, read the table and edit any
textthat needs it, then press Save and Resume. The sales rep may start the run, but only the owner may approve it. Open the draft-proposal workflow
Sam · customer care lead
Start the week knowing what customers are complaining about, how much and why, across email, tickets, payment disputes, cancellations and reviews, so the cause is fixed rather than each message answered alone.
It opens as Sam, the customer care lead.
0 of 3 steps done
Step 1. Collect the signals. Leave since empty, so the window is the last thirty days to the as-of date, and press Call customers.feedback_signals. Open customers.feedback_signals
Step 2. Find the themes. Leave since empty and press Run customers.pulse_themes. Wait for SUCCEEDED. Open customers.pulse_themes
Step 3. Compare the week. In section, choose
customersand press Call pulse.section. Open pulse.section
Answer each complaint in the tone the person's history calls for, about the right order, with any refund proposed to the owner rather than promised in the reply.
It opens as Sam, the customer care lead.
0 of 8 steps done
Step 1. Look up who wrote. In signal_id, type the complaint's signal id, such as
hubspot-ticket:planted-ticket-2, and press Call customers.customer_context. Open customers.customer_contextStep 2. Draft a reply for a first-time complaint. Type the same signal_id, leave transaction_id empty, and press Run customers.draft_reply. Wait for SUCCEEDED. Read the draft and edit it before it is approved. Open customers.draft_reply
Step 3. Draft a reply for a repeat complaint. On the same screen, type the signal id of a ticket from someone who has written several times, such as
hubspot-ticket:planted-ticket-19, and press Run customers.draft_reply. Open customers.draft_replyStep 4. Check which order is meant. Type the signal id of a ticket where two charges could match, such as
hubspot-ticket:planted-ticket-20, and press Call customers.customer_context. Open customers.customer_contextStep 5. Draft with the order named. Type the same signal_id and press Run customers.draft_reply with transaction_id empty: it is refused. Type the charge you believe is meant, from the list in the refusal, in transaction_id and run it again. Confirm the order with the customer before the reply is approved. Open customers.draft_reply
Step 6. Propose a refund. Type the signal id of a refund request, such as
hubspot-ticket:planted-ticket-21, leave transaction_id empty, and press Run customers.draft_reply. Open customers.draft_replyStep 7. Approve the reply. In signal_id, type the ticket's id. In reply_body, paste the draft exactly as you edited and read it. Press Call customers.approve_reply. Only a person approves a reply: an agent is refused. Open customers.approve_reply
Step 8. Signed in as the owner, approve the refund. In signal_id, type the refund ticket's id. Copy transaction_id, amount and Currency from the refund proposal. Press Call customers.approve_refund. Only the owner may approve a refund: the customer-care lead can propose one and is refused if she tries to approve it. Open customers.approve_refund
Answer every unanswered review politely and accurately, correcting a false claim once with the facts and without argument, and publish nothing until the customer-care lead approves it.
It opens as Sam, the customer care lead.
0 of 3 steps done
Step 1. Collect the reviews. Press Call reputation.collect. Open reputation.collect
Step 2. Draft the replies. Press Run reputation.draft_replies and wait for SUCCEEDED. Nothing is published by this run. Open reputation.draft_replies
Step 3. Approve the replies. Press New run. The run drafts one reply per unanswered review and stops at approve_replies. In the Runs tab, press Open decision. Edit any
bodythat needs it, tickapprovedfor each reply to publish, press Save under each table, then Resume. Open the review-replies workflow
Jonah · roastery and fulfilment
Find every shop order that is unfulfilled past its delivery promise, every refund left pending, and every other stalled order, each named by its order number, before the customer has to write in.
It opens as Jonah, the roastery and fulfilment.
0 of 2 steps done
Step 1. Find the orders. Press Call customers.find_order_issues. Read the rows with
issue_kindpast_promisefirst. Open customers.find_order_issuesStep 2. Read the stalled orders. On the same answer, read the other rows. The check only finds and reports: nothing is sent and no order is changed. Open customers.find_order_issues
See which items run out before a new order could arrive, read the sales rate on the right basis, and size the reorder in units, counting what is already on order, so the owner can approve the purchase order.
It opens as Jonah, the roastery and fulfilment.
0 of 6 steps done
Step 1. Open Operations, then inventory.plan. Leave as_of and lead_times empty and press Call inventory.plan. Under ANSWERED, look for rows with
statustoo late: theircover_daysis below theirlead_time_days, so they run out before an order placed today could arrive. Each row also showsavailable,velocity_7_daysandvelocity_28_days. Open inventory.planStep 2. On the same answer, find a row whose
disagreementistrue. The two sales rates differ by more than half, so the order behind the spike is shown:spike_order_id, its kind andspike_units, andvelocity_7_without_spike, the rate without that one order. The reorder is then sized on the steadier rate, inreorder_targetandsuggested_quantity. Open inventory.planStep 3. On the same answer, find a row for an item that is sold out. Its
zero_stock_days_excludedshows the days it was out of stock; those days are left out of the rate, andvelocity_28_days_rawshows the rate if they were counted as no sales. A row withreorder_on_orderhas the units already on order subtracted from itssuggested_quantity. Every figure here is a quantity; none is revenue. Open inventory.planStep 4. Signed in as the owner, open Operations, then inventory.plan, and press Call inventory.plan. Under ANSWERED,
vendor_orderslists one order per supplier, withorder_totalandminimum_order. A supplier withbelow_minimumtrueshows what reaching the minimum would take:excess_units,excess_dollarsandexcess_days_of_cover, with a note that the owner decides. The ops lead sees the same rows with the money fields empty, because the money side is the owner's. Open inventory.planStep 5. Open Workflows, then restock, and press New run. The run sizes the restock and stops at buy_list_pause; open Runs, then Open decision. In chosen_buy_list, keep or drop each line with keep, or edit its quantity; then press Save, then Resume. The run builds one purchase order and one supplier email per vendor and stops again at po_pause. Nothing is sent and nothing reaches QuickBooks. Open the restock workflow
Step 6. Signed in as the owner, on the restock run open Runs, then Open decision: the run is paused at po_pause, which only the owner may approve. In reviewed_pos, each vendor's purchase order and supplier email has its own approved tick; approving one never approves another. Tick the orders to place, and decide any order below its supplier's minimum by ticking it or leaving it unticked. Press Save, then Resume. Only the ticked orders are recorded, and the run stops again at stage_memo_pause, where the memo for the books waits for its own approval. Open the restock workflow
Each week, name the products the business holds too much of or that have stopped selling, with the stock and cash they tie up and what to do with each, so the operations lead and the owner can act before the cash is lost.
It opens as Jonah, the roastery and fulfilment.
0 of 3 steps done
Step 1. Open Operations, then inventory.plan. Leave as_of and lead_times empty and press Call inventory.plan. Under ANSWERED, look for rows with
statusoverstock: theircover_daysruns far beyond theirlead_time_days, and theirsuggested_quantityis zero, so nothing more is ordered. Every figure here is a quantity; none is revenue. Open inventory.planStep 2. Signed in as the owner, open Operations, then inventory.plan, and press Call inventory.plan. Under ANSWERED,
slow_moverslists every stocked item with no recent movement, each withon_hand,days_since_movementandcash_tied_up; the longest idle carry thelabeldead stock. A slow mover is never reordered. The operations lead sees the same rows withcash_tied_upempty, because the cash is the owner's. Open inventory.planStep 3. Open Operations, then sales.product_performance. Leave lookback_days at its default and press Call sales.product_performance. Under ANSWERED, each product in
itemshas aclassification(pushorclear), atrendagainst the period before, itsunitsand itsrevenue. The operations lead sees the same classifications and units with revenue and margin empty. The answer reads only; the owner decides what to discount, bundle or stop reordering. Open sales.product_performance
Know, weeks ahead, the last day the Holiday Gift Box packaging can be ordered and still arrive before the season starts, so the order reaches the owner for approval in time.
It opens as Jonah, the roastery and fulfilment.
0 of 3 steps done
Step 1. Open Operations, then inventory.plan. Leave as_of and lead_times empty and press Call inventory.plan. Under ANSWERED, if no season is set,
season_watchis empty andseason_notesays that no season is set: the app guesses no date. Initems, the Holiday Gift Box row shows itslead_time_days, the supplier's lead time read from the books. Open inventory.planStep 2. Signed in as the owner, open Operations, then setup.save_business_profile. Under seasons, press Add seasons, type
Holiday Gift Boxin item_or_category and the date the season starts in season_start (for example2026-11-01), and leave every other field empty. Press Call setup.save_business_profile. The season is saved on the business profile, and every other stored setting is kept as it was. Open setup.save_business_profileStep 3. Open Operations, then inventory.plan, and press Call inventory.plan again. Under ANSWERED,
season_watchnow holds the Holiday Gift Box, with itsseason_start, itslead_time_daysand itsdecide_bydate, also given in words indecide_by_in_words.season_noteis now empty. Open inventory.plan
Priya · marketing lead
Answer honestly whether the marketing is working: spend set against the online sales it can influence, the platform's claims checked against real orders, any campaign that cannot be judged named, and the biggest leak found.
It opens as Priya, the marketing lead.
0 of 5 steps done
Step 1. Open Workflows, then marketing-monday, and press New run. The run appears at the top of the run list and turns SUCCEEDED within a minute or so. The growth marketer writes one report from the growth pulse, the rating picture and the captured competitor pages; every figure is filled in by the app, and the report is filed for the owner and the marketing lead only. Open the marketing-monday workflow
Step 2. On the same screen, open Artifacts and choose marketing_monday.
heldisfalse. The pulse paragraph gives each view's status, red, amber or green. It then names the sized problems, each with what it is worth a month, largest first: these are the things to do. Open the marketing-monday workflowStep 3. Open Operations, then growth.pulse, and press Call growth.pulse. Under ANSWERED, find the view Funnel from lead to won. If it is red, it names the pair of stages where the most deals drop out, and the share of deals that entered the first stage and never reached the second.
online_revenue_last_30_daysgives the recent online revenue, and every rate names its numerator and its base. Open growth.pulseStep 4. Open Operations, then ads.read_account, and press Call ads.read_account. Under ANSWERED,
attributionsets each campaign's claimed conversions beside the shop's tagged orders, in a sentence that says how far apart they are. Undercampaigns, a campaign without conversion tracking haslabelno verdictand areasonthat says so: it cannot be judged, and the answer says so. Open ads.read_accountStep 5. Open Operations, then ads.return_on_online_revenue, and press Call ads.return_on_online_revenue. Under ANSWERED,
ad_spendsits besideonline_revenue_sor, the online revenue the ads can influence, andverdictgives the dollars of online revenue per ad dollar.company_revenueis shown so you can see it, and it is never the base of the return. Open ads.return_on_online_revenue
Find the ad that has stopped paying its way, with both comparisons and its frequency in view, and decide whether to pause it, knowing what that saves a month.
It opens as Priya, the marketing lead.
0 of 3 steps done
Step 1. Open Operations, then ads.read_account, and press Call ads.read_account. Under ANSWERED, look for a campaign with
labelproblem. Itsreasonstates both comparisons: its cost per result against the account's own average, and against the campaign's own past, plus how often the same people have seen it, and what pausing it saves a month. Its row also showsspend_30,results_30andmonthly_saving_if_paused. The comparison with the account sets the label; the reason states both. Open ads.read_accountStep 2. Open Operations, then ads.recommend, and press Run ads.recommend. The run appears under the button and turns SUCCEEDED within a minute or so. In its answer, the problem campaign's recommendation has
actionpause, awhatsentence, its spendtodayandafter, thenetchange, andreversibletrue. The campaigns that are doing well are kept as they are, and any campaign without conversion tracking is listed undercannot_be_judged. Nothing is changed in the ad account. Open ads.recommendStep 3. Open Workflows, then ad-changes, and press New run. The run drafts what to do for each campaign that has a verdict and stops at review_ad_changes, one pause that lists every change. In the Runs tab, press Open decision. In
approved_ad_changes, find the row withactionpause, itsnetandreversibletrue. Tick itsproceedbox;ad_approval_metais already filled with your sign-in and the time. Press Resume once, which saves your edits first. The run turns SUCCEEDED, andad_change_recordholds one row for that campaign withstatussimulated_changed; nothing is sent to the ad platform. Open the ad-changes workflow
Build the month's content around the products that are selling, hold back a product that draws complaints, see stock and missing photos before anything is promoted, and approve the posts that go ahead.
It opens as Priya, the marketing lead.
0 of 6 steps done
Step 1. Open Operations, then campaigns.start_from_sales. Type the month's discount code in discount_code and its tracking tag in utm_tag, and press Call campaigns.start_from_sales. Under ANSWERED, the draft names two or three products to push (
pushed), the slow products to bundle (bundled), and, listed apart undertroubled, any product drawing complaints, which is never pushed. Every product it considers with under two weeks of stock cover is listed inflagged, with its stockout date instockout_dates, read from the stock plan. The draft is stored with status draft; nothing is sent. Open campaigns.start_from_salesStep 2. Open Operations, then campaigns.plan_calendar. In campaign_id, type the id the previous step returned. In channels, type
instagram_feedand press Enter, thenemailand press Enter. Leave start_date empty to start on the campaign's own window start, and press Run campaigns.plan_calendar. When the run turns SUCCEEDED,rowsholds the campaign's calendar: the growth marketer chooses which product goes on which channel, and the app sets the days (Monday, Wednesday and Friday), each row'spath(designfor a picture channel,text_onlyfor email) and any same-product, same-dayconflict.design_rowsandtext_only_rowscount them. Planning again replaces the calendar. Nothing is published. Open campaigns.plan_calendarStep 3. Open Operations, then campaigns.asset_manifest. In campaign_id, type the campaign's id and press Call campaigns.asset_manifest. Under ANSWERED, each design row of the calendar lists its image slots: a photo on file, or missing when no photo of that product exists. A missing slot is never filled with another product's photo, and the row is not ready for design until you choose what to do with it. Open campaigns.asset_manifest
Step 4. Open Operations, then content.calendar, and press Run content.calendar. The run turns SUCCEEDED. The growth marketer proposes rows for the four weeks after the shop's as-of date, and the app adds only the slots the calendar does not already hold. A row you have edited or deleted is never rewritten, every price is the shop's own, and two rows for one product on one day are flagged. Nothing is published. Open content.calendar
Step 5. Open Operations, then content.draft_posts. In as_of, type the moment to draft from (for example
2026-09-14T09:00:00-07:00), and press Run content.draft_posts. The run appears under the button and turns SUCCEEDED in about a minute. Underdrafts, each coming calendar row has one draft in its channel: anemaildraft has a subject, a preheader and a body, and adesign_requestdraft has a caption and hashtags. Each price is the shop's own. A draft written without voice samples carries a note saying so. The growth marketer words each draft, so the wording differs from run to run. Nothing is posted or stored. Open content.draft_postsStep 6. Open Workflows, then content-posts, and press New run. The run drafts one post for every calendar row after the shop's as-of date and stops at review_posts. In the Runs tab, press Open decision. The table
reviewed_postslists every draft, each withselectedtrue. Press Remove on any post that should not go ahead and press Save under the table; check thatapproval_metaholds your user id, press Save under it, then Resume. The run turns SUCCEEDED, andpost_resultrecords each post left in the table assimulated_post, with its channel and a label saying where it would be sent. A post whose time has passed, or one that is held, is refused by name. Nothing is posted. Open the content-posts workflow
Send a campaign to the subscribers who have stopped ordering, with anyone who complained recently left out and named, have the owner approve it, and afterwards read what it changed against the fortnight before.
It opens as Priya, the marketing lead.
0 of 6 steps done
Step 1. Open Operations, then campaigns.start_from_sales. Type the campaign's discount code in discount_code (for example
ETHIOPIA15) and its tracking tag in utm_tag, and press Call campaigns.start_from_sales. Under ANSWERED,campaignis the stored draft, with status draft, the products it pushes and bundles, and itscampaign_id. Nothing is sent. Open campaigns.start_from_salesStep 2. Open Operations, then campaigns.define_audience. In campaign_id, type the id the previous step returned. In segments, type
subscription-customers-no-order-60-daysand press Enter, then press Call campaigns.define_audience. Under ANSWERED, the segment'scountis the subscribers whose last successful charge is more than two months old;excludednames each one held back by a recent complaint, matched by customer or by email; andsendable_countis what is left. Nothing is sent and nothing is stored. Open campaigns.define_audienceStep 3. Open Operations, then campaigns.stage. In campaign_id, type the campaign's id. Press Add drafts once for each post, email and design request, giving each its draft_id, kind, channel, scheduled_at, subject and text, with the email's audience_segment set to the segment of the previous step. In as_of, type the moment to stage from (for example
2026-09-14T09:00:00-07:00); left empty, it is the real clock, and any draft dated before it is refused as past. Press Call campaigns.stage. Under ANSWERED,stagedlists each draft held for approval, an email with the recipient count the app computes from its segment. A draft scheduled at or before now, or with an image slot still missing, is listed underrefusalswith its reason. Nothing is approved or sent here. Open campaigns.stageStep 4. Signed in as the owner, open Workflows, then campaign-staging, and press New run. The run takes the oldest staged draft and stops at approve_draft. In the Runs tab, press Open decision. The draft's
amountis its recipient count, computed by the app; a large send may be approved only by the owner. Check thatapproval_metaholds your user id, press Save under it, then Resume. The run turns SUCCEEDED, andapproval_recordrecords who approved, when, the recipient count and a sentence saying the send was simulated. Nothing is sent. A run with no staged draft ends without a pause. Open the campaign-staging workflowStep 5. When the campaign's window has passed, open Operations, then campaigns.results. In campaign_id, type the campaign's id and press Call campaigns.results. Under ANSWERED,
redemptionscounts the charges that carried the code,code_signupsthe subscriptions signed up with it, andproductsgives each pushed product's revenue in the window, the fortnight before and the same dates last year, with the change against each. Every product row carries the note that a change is inferred, not proved to be the campaign's, and there is no total across products. A campaign whose window has not started reads "no results yet". Open campaigns.resultsStep 6. Open Operations, then campaigns.explain_results. In campaign_id, type the campaign's id and press Run campaigns.explain_results. The run turns SUCCEEDED. The growth marketer writes one paragraph on what worked and what did not; every figure in it is filled in by the app from the results, an inferred figure is worded with a hedge, and any unsubscribes are mentioned. The wording differs from run to run. A paragraph that breaks those rules is held, with the reason, and carries no explanation. Open campaigns.explain_results
See what stops search engines and AI assistants from reading the business, with each fix ready to paste, and read the rating trend and a competitor's recent moves alongside it.
It opens as Priya, the marketing lead.
0 of 4 steps done
Step 1. Open Operations, then visibility.audit, and press Call visibility.audit. Under ANSWERED,
findingslists each problem in order, each with itsimpact, itseffortand the date the site was captured, never a score. Look for high-impact findings such as an AI crawler blocked from the shop byrobots.txt, pages that show their content only through JavaScript, opening hours on the site that disagree with the listing (the listing is taken as the true one, and the site text is what gets fixed), missing LocalBusiness structured data and a missingllms.txt.robots_correctedandlocal_business_jsonldhold the corrected files, every value read from the listing. Open visibility.auditStep 2. Open Operations, then visibility.write_fixes. Leave request empty and press Run visibility.write_fixes. The run turns SUCCEEDED within a minute or so. Under
drafts, one file per fix is ready to paste, each naming the finding it fixes: for examplerobots.txt, letting the AI crawlers read the site;schema, the LocalBusiness block with the opening hours;about-page-hours, the hours line for the About page; andllms.txt, a plain description of the business for AI assistants. Every name and hour is taken from the listing.heldis empty. Nothing is changed on the site. Open visibility.write_fixesStep 3. Open Operations, then reputation.collect, and press Call reputation.collect. Under ANSWERED,
ratingshows the recent average,average_last_90_days, against the period before (trend_previous), withtrend_directionandtrend_statusin red, amber or green. If the rating fell,drop_reviewslists the low reviews behind the drop, so you can read what they share.unansweredholds the reviews still waiting for a reply. Open reputation.collectStep 4. Open Operations, then growth.marketing_monday, and press Run growth.marketing_monday. The run turns SUCCEEDED in about a minute. In its answer,
brief.competitors_changedreports what each competitor's captured page shows, labelled Observed, with the page's capture date. A separate sentence labelled Inference says what that may mean for the business.brief.customers_saidgives the rating figures of the previous step. The growth marketer words each sentence, so the wording differs from run to run; the figures and dates are the app's. Nothing is filed. Open growth.marketing_monday
See the tables behind WidgetCo's payments: what each one holds, where its data comes from, and its rows, before trusting a number built from them.
It opens as Dana, the owner.
0 of 5 steps done
Step 1. Open the tables. Open tables
Step 2. Find the group payments and read its list: each table with its row count, and a ✓ when it found its data.
Step 3. Open settlements, the one view of money received from both PayPal and Stripe. Open settlements
Step 4. Read its columns:
processor,occurred_at,settled_at,gross,fee,net,payer_nameand the rest, and the tables it is built from.Step 5. Scroll the preview of its rows.
Browse the money WidgetCo has received, then turn it into a table of totals by processor and week.
It opens as Dana, the owner.
0 of 6 steps done
Step 1. Open the data browser. Open data
Step 2. Choose the model payments and open the table settlements. Open settlements
Step 3. Sort by
settled_at, newest first. Add a filterprocessor=stripeto see one processor, then remove it.Step 4. Open the pivot. Open the pivot
Step 5. Choose the table settlements. Put
processorin rows andweek_bucketin columns, and add the measure Settled Gross as the value.Step 6. Save it as a view, named for example
Money in by processor and week.
Find the failed or pending payments over an amount you choose, using a question the payments model already carries.
It opens as Dana, the owner.
0 of 4 steps done
Step 1. Open the data browser. Open data
Step 2. Under Saved queries, find Which failed or pending payments are over a given amount? and press Run.
Step 3. In the form, type the smallest amount you care about in threshold, for example
200, and press Run.Step 4. Press Run again in the query screen to see the rows. Open queries
Write your own question over the payments data, run it, and save it so you or others can ask it again.
It opens as Dana, the owner.
0 of 5 steps done
Step 1. Open the query screen for payments. Open queries
Step 2. Type a question over the model's tables, for example the fees each processor charged:
SELECT processor, SUM(gross) AS gross, SUM(fee) AS fees, SUM(net) AS net FROM settlements GROUP BY processor ORDER BY gross DESCStep 3. Press Run.
Step 4. Press Save, give it a question in plain words, such as
What did each processor charge us in fees?, and a one-line description.Step 5. Go back to the data home and find it under Saved queries. Open data
Add one of smb-pulse's data models to the organisation.
It opens as Dana, the owner.
0 of 5 steps done
Step 1. Open the data models. Open data models
Step 2. Press Add model and choose a template, for example calendar. Add it.
Step 3. Read the app's answer: it names the table group the model brought with it, and how many tables.
Step 4. Open the tables to check they found their data. Open tables
Step 5. Open the model to see its tables, relationships and measures. Open the model
Tell a table where its rows come from when it has not found its data, and check the connection before saving it.
It opens as Dana, the owner.
0 of 5 steps done
Step 1. Open the tables. Open tables
Step 2. Find a table marked ✗, or open a group's Connect your data, for example for payments. Connect payments
Step 3. For each table, choose its source: a file, or a table inside a database file.
Step 4. Match the table's columns to the source's columns.
Step 5. Press Check. Fix any column the check names, then press Save.
Run a model's data rules against the organisation's real files, and read what passed and what did not.
It opens as Dana, the owner.
0 of 5 steps done
Step 1. Open the model, for example payments, and open Checks: the declaration check (is the model itself well formed) and the data check (does the data obey the model's rules). Open the model
Step 2. Open the operation that runs the data rules. Open models.check_data
Step 3. Type the model's name,
payments, in model, and press Call models.check_data.Step 4. Read the answer:
checked(how many rules ran),sound(true when every rule passed), andbroken, one entry per rule that failed.Step 5. Go back to the model and read Checks again. Open the model