GoodOps Module slices · internal
Oct 2026
Where we are

Two complete slices. Every module gets the same four pieces.

A slice is everything one module needs to be sold end to end: a page that sells it, a sell sheet to send, an intake that captures what the client wants and uses, and the proposal with the blueprint and roadmap that comes back. Voice Memory and Receipts & Expenses have all four, plus the team's map of how it runs. The job now is the same slice for the other ten, so the audits get deeper: the AI Readiness Blueprint first, then Knowledge, Design System, the rest, and finally the 360 dashboard.

01 · The Voice Memory slice

Four pieces, done.

Click through in order to see the client's journey: they read the page or the sell sheet, fill the intake, and receive the proposal.

PIECE 1

Landing page

Module 01 on the site. Three stages, the four states, house rules, the 8-week plan, CAD 10–20k. One CTA: book the call.

For the prospectOpen the page all 12 · print to pdfPIECE 2

Sell sheet

Two pages for people who never saw the landing page: the pitch, then what's delivered and the price. One template, every module, pick and print. The original Voice Memory PDF is here.

For the prospect to forwardOpen the sell sheet operator view: ?role=opPIECE 3

Intake form

Opens on the booking confirmation. Eight outcomes (Want / Not needed / Have / Not sure), every place voice happens, who else to ask. Shared link, autosaves, Send button.

For the client, before or on the callOpen the intake worked examplePIECE 4

Proposal: blueprint + roadmap

Lands 30 minutes after the call. Stage today, outcomes with go-live weeks, the four-state plan, connections, the work, roadmap, house rules, done-means, one fixed price. Rendered from the intake and the call.

For the client, after the callOpen the proposal
Behind the slice · for the teamHow it worksThe service flow, the twelve-step swimlane of who does what and what's automated, the data model (CRM, database, catalogs), and the emails along the way, E1–E8.
Open the map
02 · What a slice is

The same shape, every time.

  1. 1
    Landing pageSells one module. Stages today, the four states, the plan, the price band. Exists for the first eleven; module 12 needs one.
  2. 2
    Sell sheetTwo printable pages, same words as the landing page, for people who never saw it. Page one is the pitch; page two is what's delivered and the price. The thing that travels inside the client's organization.
  3. 3
    Intake formThe module's specific outcomes (Want / Not needed / Have / Not sure) and the places or tools it touches. Same shell as Voice Memory; only the catalogs change. Shared answers carry over, so a second module starts half-filled.
  4. 4
    Proposal: blueprint + roadmapWhat comes back after the call. The module's outcomes with go-live weeks, its tool verdicts, its work and gates, one price. Same renderer; the module supplies the template.
  5. +
    How it works, for the teamService flow, swimlane, data model, emails. Shared across modules; each module adds catalogs and verdict rules.

Why slices, not features.

A slice can be sold on Monday. A pile of half-built modules can't. Each slice also teaches us something about the shared machine: Voice Memory gave us the intake shell, the proposal renderer, the CRM mapping and the catalogs. Module two should take a third of the time. Module five should be mostly content.

Intakes merge

Ask once. Every module after the first starts half-filled.

Organization, people, tools, stack, consent and stage are answered once and live on the organization, not on the intake. A second module's intake opens with all of that already there and asks only its own outcomes. How many modules a client wants decides what the intake is called and what comes back: Anything we already know from enrichment, a previous call or a connected tool is pre-ticked and marked where it came from, so the client confirms instead of retypes.

1–4 modulesCombined intakeOne link, one call, one proposal with a chapter per module. Bundle rate.
5 or moreAI Readiness + Opportunities BlueprintThe initial audit. Every chosen module's intake under one slug, scored by stage, one roadmap that says which module first.
All twelve360 DiagnosticThe dashboard. Every module's stage, stack health, every health indicator, the full roadmap, refreshed quarterly.
  • Already a client? The quarterly re-run and any new module share the same organization record; the call is a check-in, not a discovery.
  • Several modules at once? Up to four: one intake link with several outcome sections, one call, one proposal with the modules' sum at a bundle rate. Five or more: it stops being a bundle and becomes the Blueprint, scored and ranked, because at that size the question is "which first," not "these please."
  • Tools connected? If they've granted access (Workspace, HubSpot, Asana), the tools step is pre-filled from what's actually there, including which features are switched on.
03 · Next: all eleven

One slice per module, in the order clients ask.

Landing pages exist for the first eleven; module 12 is new. Two slices are complete and every module now has a sell sheet; the dots link to each finished piece. Intakes for the other modules are one setting each, since all twelve live in the intake's registry. Suggested order is by how often the problem comes up in discovery calls; reorder as the calls teach us otherwise.

Intakes merge · live exampleVoice Memory + Receipts & Expenses, one intakeSixteen outcomes in two groups, one merged tools list (voice places and money places, deduplicated), one brief with a chapter per module, one Send. Same code as the single-module intakes; the module set is baked in per link (or ?modules= on Netlify).
Open the combo →
#ModuleLanding pageSell sheetIntakeProposalNotes
01Voice MemoryComplete slice. Dots link to each piece.
02Receipts & ExpensesSecond complete slice (Oct 7). Dots link to each piece. Intake shares the code with Voice Memory.
07One Client RecordNatural second: Voice Memory feeds it (CRM updated from calls). Intake = where client data lives today.
06Quote to KickoffThe parked "proposal drafted from the call" outcome lives here.
05AI, Switched On ProperlyIntake = which AI tools are on, who has seats, what the rules are.
08Flowing DocumentsWritten-knowledge twin of Voice Memory. Same brain.
03Time Tracking
04Invoicing
10Employee OnboardingThe "new hire reads the full history" outcome points here.
09Backups
11Protected WorkplacePairs with the IT + AI Security Assessment.
12Software Migration + Activation newThe catalogue module: any tool verdict, anywhere, becomes a line item here. See below.
Module 12 · Software Migration + Activation

The module that catalogues every other verdict.

Every intake ends with a four-state plan: Activate, Optimize, Migrate, Good to go. Today those verdicts only become work when they sit inside a module like Voice Memory. Module 12 makes each one a product in its own right, so the full roadmap can price and schedule everything we'd touch, whether or not a bigger module is attached.

What it is

A catalogue of small, fixed-scope jobs keyed to the tool catalog: switch on Meet transcription for everyone; move 14 months of recordings out of Fathom; retire Zoom; consolidate three note tools into one; connect HubSpot to the memory. Each job has a verdict, a tool, hours, a price and a done-means line.

Its intake

Mostly already answered: the tools step from any other module plus one question per tool — keep it, fix it, move off it, or switch it on. Runs on its own as a quick “clean up my stack” engagement, or rides inside the AI Readiness Blueprint as the section that turns findings into a priced list.

Its proposal

The four-state board as line items with hours and price, grouped by week. In a combined proposal it's the appendix every other chapter points at; alone, it's the whole thing. This is also how the 360 dashboard counts stack health: tools by state, over time.

Why it matters for the roadmap

It lets us say yes to the small things without inventing a module each time, keeps every service in one catalogue, and gives the retainer a backlog: the Optimize and Migrate items a client didn't buy yet.

Activate switch on what they ownOptimize connect what's already onMigrate move history, retire the restGood to go leave alone, plug in
04 · The goal: more modules, deeper audits

Every module we add makes the audits more complete.

A module is a slice we can sell on its own. An audit is several intakes run together, scored, and laid out as one roadmap. More modules means more sections in the audit and more of the roadmap we can actually deliver. The path, in order:

  1. 1
    AI Readiness + Opportunities BlueprintOur initial audit. Where the organization is on every module's stages, what's switched off, where the hours go. Output: a blueprint and a ranked list of modules to start with.Sold today as the AI & Operations Diagnostic · intakes: 01, 05, 06, 07 first
  2. 2
    Knowledge Audit + PlanWhere knowledge lives, where it leaks, who holds it in their head. Voice Memory, Flowing Documents and Employee Onboarding intakes together.Pilot delivers · intakes: 01, 08, 10
  3. 3
    Design System + PlanBrand, components, templates and how AI can produce on-brand work. Its own intake: what exists, what's used, what's drifted.Pilot delivers · intake to build
  4. 4
    The othersIT + AI Security (Protected Workplace, Backups, AI Switched On), Finance (Receipts, Invoicing, Time), Sales (Quote to Kickoff, One Client Record). Each a bundle of intakes with its own plan. Module 12 sits under all of them as the priced tool list.Bundled as the slices land
  5. 5
    360 full business auditEverything, in one dashboard. Every module's stage, stack health by the four states, every health indicator, the full roadmap, the retainer plan, refreshed every quarter from the re-run intakes.The dashboard · needs all twelve slices
Two kinds of data points

Most intake answers point at a module: Want + a tool that's off → Activate. Some don't; they're health indicators. Hours spent on recaps, how many places history lives, whether anyone can opt out of recording. They go on the dashboard as a reading, not a recommendation. The catalogs mark which is which.

What carries over

The intake shell, shared link and Send, the operator view, the four-state verdicts, the proposal renderer, the CRM objects and the database tables. None of it is Voice-Memory-specific; it reads from catalogs.

What the audits add

A combiner: several intakes under one slug, a stage score per module, health indicators scored against a band, ranking by Want and top two, and the proposals laid end to end as phases of one roadmap with one price. The 360 is that combiner over everything, kept live.