Owner-operator SMB after losing key staff

Scoping no longer lives in one person's head

Rooted is in a state where a lead can come in, get a site assessment, get a quote, and get a plant spec without the departed designer being in the loop. The knowledge that left in March is now sitting in a written system that you, the crew lead, or a trained staffer can run.

Why this matters: This is the single failure point that took quote turnaround from 2 days to 11 and is bleeding 40% of design leads. With spring six weeks out and both leases on your name, this is the state-change that decides whether the season happens.

How they'll know it's real: Twelve months from now, a lead that comes in on a Tuesday has a site assessment booked and a quote with plant spec in the homeowner's hands inside 2 days — and the person who did it was not you alone and not a replacement star designer.

Because you said: Buyer Outcome · Catalyst · Identity

The crew installs the right plants for the site, the first time

Rooted is in a state where the crew lead receives a site→plant spec sheet that tells them what goes where and why, tied to the actual soil, light, and water conditions you co-designed around. Warranty replacements stop being a cost of doing business and go back to being the rare exception your year-one guarantee was built around.

Why this matters: Warranty redos are eating margin right now because specs are guesses. Your whole identity — selling horticultural judgment, not SKUs — depends on the plant actually surviving. If the crew keeps guessing, the guarantee becomes the thing that kills you instead of the thing that sells you.

How they'll know it's real: Twelve months from now, the crew lead is pulling a spec sheet for each job before they roll, and warranty replacement cost per install is materially down from where it sits today.

Because you said: Stakeholders · Identity · Catalyst

Every Monday, you know where every project stands

Rooted is in a state where there is a weekly rhythm — a single view, on Monday — that tells you which stage each project is in: lead, assessment booked, quote out, accepted, scheduled, installed, in warranty. The bookkeeper sees the same picture live instead of reconstructing it after the fact.

Why this matters: You're the only person who talks to both locations and the crew lead, you decide everything alone, and admin lives in the cracks of a 55-hour field week. You asked for this rhythm by name. Without it, you stay the bottleneck and quoting keeps happening at 11pm.

How they'll know it's real: Twelve months from now, Monday morning takes you under 30 minutes to know the state of every active project, and the bookkeeper closes job costs in the same week the job finishes — not months later.

Because you said: Buyer Outcome · Stakeholders · Buyer

The homeowner experience matches what you promise

Rooted is in a state where a homeowner who reaches out gets a guided assessment and a quote within 2 days, and feels handled the whole way through. The 11-day silence that's losing leads to faster competitors is gone.

Why this matters: Your five-year picture is being the Asheville name people are referred to and booked a season ahead. That reputation is built one homeowner at a time, and right now each lost lead is also a lost referral. The bedrock you named — trusted horticultural judgment — only compounds if homeowners actually experience it.

How they'll know it's real: Twelve months from now, design-lead-to-quote conversion is back up, the share of new business coming from referrals is rising, and homeowners are describing the assessment itself as the reason they chose Rooted.

Because you said: Stakeholders · Catalyst · North Star

The business runs on a system, not on you

Rooted is in a state where the assessment-and-spec system is the thing customers and staff rely on — not your personal availability. The 2-3 tools you chose are set up, working inside your hard limits (no developer, no command line, doesn't break Square, no evening fiddling), and the crew lead and bookkeeper operate inside them without needing you to translate.

Why this matters: Your five-year picture is three locations run by a trained team while you work on the business, not in it. That picture is only reachable if the system — not the owner — is what's repeatable. It also has to be reachable from inside ~4 admin hours a week in season without draining you to abandonment.

How they'll know it's real: Twelve months from now, you can be off the floor for a week in season and quotes still go out, specs still get cut, and Monday's project view still updates — because the system, not your phone, is holding it together.

Because you said: North Star · Buyer · Constraints · Buyer Outcome

The physical floor: what the operation can actually deliver

Rooted's hard ceiling is one crew lead doing installs, you doing everything customer- and decision-facing, and a part-time bookkeeper. There is no designer in the building. With spring at 60% of annual revenue starting in 6 weeks, the throughput cap on design-installs is whatever site assessments + plant specs you and the crew lead can personally produce, plus whatever the floor staff can intake. That is the real capacity — not the 11-day quote backlog, which is a symptom of overshooting it.

Why this matters: Every fix you consider has to fit through this hole. A scoping system that still requires a designer-grade brain at the spec step will fail in week one, because that brain left in March.

How they'll know it's real: Spring quotes either come out within the 2-day target with you and the crew lead inside your hours, or they don't. There is no third option.

Because you said: Identity · Catalyst · Constraints · Stakeholders

What you can see right now without asking someone

Today the only live system you personally read is Square (sales) and your inbox/Instagram (leads). You cannot currently see: where any given design lead is in the pipeline, which quotes are aging, what the crew lead is about to install this week, or job-level cost as it happens. The bookkeeper reconstructs job costs after the fact, meaning current state of a project is not visible to anyone — it's reassembled later. So 'what's the status of every project' is, right now, unanswerable without phone calls.

Why this matters: Your Monday rhythm outcome (F3 #3) is literally a visibility outcome. You can't get it by working harder; you get it by making project stage readable somewhere you and the bookkeeper both look.

How they'll know it's real: On a Monday morning, can you name the stage of every active design lead without texting the crew lead? Today: no.

Because you said: Buyer Outcome · Buyer · Stakeholders

What the team can actually execute today (not what's claimed)

Honest read of execution capacity: (a) Floor staff can intake a lead but cannot scope a site or spec plants. (b) Crew lead can install and could be trained to capture site conditions (soil, light, water) on a structured form, but currently guesses plant specs and absorbs the warranty cost when wrong. (c) You can do horticultural judgment but only in the cracks of a 55 hr/wk in-season schedule, and admin drains you fast. (d) Bookkeeper handles numbers but works after the fact. Nobody on payroll can today run lead→assessment→quote→spec end-to-end. That is the gap the departed designer used to close.

Why this matters: The repeatable system in F3 has to split the designer's old job into pieces small enough that the people you actually have can each hold one piece. If any step still needs designer-level judgment, the system doesn't work.

How they'll know it's real: A lead comes in Tuesday. By Thursday, a quote with a plant spec sheet goes to the homeowner, and no single step required a person Rooted doesn't currently employ.

Because you said: Catalyst · Buyer · Constraints · Stakeholders

What the money allows

The economic envelope for the fix is tight and explicit: ~$200/mo recurring software before it has to pay for itself, ~$500 one-time, no developer, no paid setup help. Against that: you're losing ~40% of design leads to faster competitors and eating warranty replacements on wrong-plant installs. So the financial truth is that the cost of the current broken state is already much larger than the $200/mo budget — but the budget for the tool stack itself is real and non-negotiable, because anything above it requires the fix to already be working to justify itself.

Why this matters: This rules out most 'real' CRM/project tools and rules in lightweight, no-integration setups. It also means the 2–3 tools chosen for you (F3 #2) have to be picked against this ceiling, not aspirationally.

How they'll know it's real: Total recurring software for the scoping + visibility system stays at or under $200/mo, and setup happens without a developer or evening work.

Because you said: Constraints · Catalyst · Buyer Outcome

What has to be load-bearing for the five-year picture

The North Star is Rooted being the referred name for horticultural judgment, three locations, booked a season ahead, run by a trained team on the assessment-and-spec system. The load-bearing thing across that picture is not tools and not volume — it's that horticultural judgment lives in a documented system the team runs, not in one person's head. The March departure already proved what happens when it doesn't. So every choice in the spring fix either deposits judgment into the system (site checklist, plant-spec rules, warranty learnings captured) or it doesn't, and only the depositing ones count toward year five.

Why this matters: It tells you how to judge any fix this week: if it solves spring but keeps the knowledge in your head, you've just become the next single point of failure. The reputation you're building requires the opposite.

How they'll know it's real: A new hire next year can produce a correct site assessment and plant spec by following the written system, and warranty-replacement rate trends down — both without you in the room.

Because you said: North Star · Catalyst · Identity · Buyer Outcome

How your recommendations are built (not from a template)

Every tool, sequence, and move recommended to you is derived from your specific outcome — a repeatable lead→site-assessment→quote→plant-spec system that runs without the departed designer — and your specific limits: 4 admin hrs/wk in season, $200/mo, no developer, cannot break Square. You will not be handed a generic 'small retail starter kit' or a 'landscaper stack.' If a popular tool fails your constraints (e.g. needs a developer, or replaces Square), it is excluded for you even if it's the standard recommendation elsewhere.

Why this matters: You have 6 weeks to spring and you decide alone. A template would waste your only window on tools that don't survive your reality (Square lock-in, no evening setup, energy drain from fiddling).

How they'll know it's real: Every recommendation you receive cites which of your constraints or outcomes it serves. If it can't cite one, it isn't recommended.

Because you said: Buyer Outcome · Constraints · Buyer

The order moves are handed to you

Moves are sequenced against your catalyst clock, not delivered as a flat list. Scoping + plant-spec (the thing collapsing right now) is sequenced before anything else — including weekly rhythm dashboards or bookkeeper visibility — because spring is 6 weeks out and 40% of design leads are leaking now. The 'first three moves this week' you asked for in F3 are the front of this sequence; project-stage visibility and bookkeeper live-view come after the bleed is stopped.

Why this matters: You work in 4-hr admin weeks. If sequencing is wrong you'll spend week one on a Monday dashboard while leads keep walking to faster competitors.

How they'll know it's real: Each move you're given has a 'do this before / after' marker tied to the spring deadline, not a generic priority score.

Because you said: Catalyst · Buyer Outcome · Constraints

What a tool has to prove before it's even eligible

Before any tool reaches your shortlist, it must clear your hard limits: no developer needed, no command line, no Square replacement, setup completable in daytime hours by a non-technical operator, under your $200/mo + $500 one-time envelope, and operable by a crew lead and bookkeeper — not just by you. Tools that can't demonstrate all of those are filtered out before you ever see the name. You won't be asked to evaluate options you couldn't actually run.

Why this matters: The word 'integration' makes you anxious and daily fiddling = abandonment. If a tool gets past this gate, you can trust it survived the filter you would have applied yourself if you had time.

How they'll know it's real: The shortlist you receive is 2–3 tools (matching your F3 ask), each with the constraint-check shown.

Because you said: Buyer Outcome · Constraints · Buyer

When a tool gets pulled back out

A tool that's already in your stack gets removed when it starts costing you the things you bought it to protect: your 4-hr admin budget, your evenings, your Square setup, or your crew lead's ability to run it without you. If a recommended tool drifts (price hike past $200/mo, a new version that demands command-line setup, an update that breaks Square), it is flagged for removal — not defended because it's already installed.

Why this matters: You can't afford to keep a tool just because you already learned it. Your time and energy are the scarce resource, not the switching cost.

How they'll know it's real: Each tool in your stack has a 'pull condition' written next to it in plain English.

Because you said: Constraints · Buyer

When the tool landscape shifts under you

Plant-and-garden retail software and small-contractor quoting tools change pricing and features constantly. The apparatus responds on your behalf — it does not ask you to monitor the market. The trigger to revisit is your operation breaking (quote turnaround climbing again, crew lead can't run the spec sheet, bookkeeper loses live view), not a vendor announcement. You will not be sent 'new feature' updates that demand your attention in season.

Why this matters: In season you have 4 hrs/wk. You cannot be the person tracking whether your quoting tool just got acquired.

How they'll know it's real: You get notified only when one of your own operational signals trips, not on vendor cadence.

Because you said: Constraints · Catalyst

Building you the whole system, not patching the worst leak

The departed-designer hole could be patched narrowly (just a quote template, just a plant list). The decision here is to build the full lead→assessment→quote→plant-spec→install loop you described in F3, not just plug the loudest leak. Reason: you've told the method the five-year state is a trained team running the system across three locations — a patch won't survive that. The build is staged so spring is protected, but it's a build, not a band-aid.

Why this matters: A patch gets you through spring and traps you again next March when the next key person leaves. The system you described in F7 requires the comprehensive version.

How they'll know it's real: The deliverable names every stage of your lead-to-install loop, not just 'quoting.'

Because you said: Buyer Outcome · North Star · Catalyst

When 'going above and beyond' is treated as an alarm

Your business sells horticultural judgment with a one-year planting guarantee. If the apparatus catches the crew or you compensating for a bad spec by overdelivering — extra free plants, extra site visits, eating warranty redos at scale — that is treated as a signal the spec system is failing, not as good customer service. The fix is upstream (the assessment + plant-spec sheet), not downstream (more free replacements).

Why this matters: You're already eating warranty replacements because the crew guesses plant specs. Left unflagged, overdelivery hides the real failure and bleeds margin into spring.

How they'll know it's real: Warranty replacement rate and 'free extras given' are tracked as a system health indicator, not absorbed silently.

Because you said: Identity · Catalyst · Stakeholders

When you move from 'surviving spring' to 'running the system'

You are in a survival stage right now (catalyst: designer gone, spring in 6 weeks, leases personally guaranteed). The apparatus holds you in survival mode — short moves, daily-readable, no optimization work — until specific exit conditions are met: quote turnaround back under 3 days, crew lead running plant-spec without you, Monday project-stage view actually being read. Only then does it shift you into the next stage (training the team, preparing the third location). You won't be pushed to 'optimize' while you're still bleeding.

Why this matters: If you're handed five-year roadmap work in week two, you'll abandon it and the spring fix both. The stage gate protects the sequence.

How they'll know it's real: You're explicitly told which stage you're in and what trips the transition.

Because you said: Catalyst · Buyer · North Star

The shape of the help you're getting

You asked for tools chosen for you, set up without hiring tech help, and the first three moves this week. The decision is to deliver as a done-for-you-decision, do-it-yourself-execution shape: the method makes the calls (which tools, which sequence, what to drop), you and your crew lead execute in daytime hours. It is not consulting calls, not a course, not a build-it-for-you install. That shape is locked because anything heavier breaks your no-evenings / no-developer / energy-drain constraints, and anything lighter (just a reading list) doesn't survive your 6-week clock.

Why this matters: You need to know what kind of help this actually is before spring, so you don't wait for a consultant who isn't coming or a course you don't have evenings for.

How they'll know it's real: Every deliverable is a decision + an execution step a non-technical operator can do in daytime, not a meeting or a curriculum.

Because you said: Buyer Outcome · Buyer · Constraints

Cohort admission

N/A for you because your intake is a single-owner, single-business engagement — there is no cohort or group context in your inputs that this decision bears on. If you later expand to running the system across a third location with multiple trained operators, this decision becomes live.

Because you said: Identity · Buyer

1. Your Monday command center — the one screen that shows every project's stage

A single view (a shared spreadsheet or a simple pipeline tool like Trello/Notion will do) where every lead and job sits in a column: New Lead → Site Assessment Booked → Assessment Done → Quote Sent → Won/Lost → Installed → In Warranty. You glance Monday morning and know where everything is without asking anyone.

Why this matters: You told me the deliverable is 'every Monday I know every project's stage' and that admin lives in the cracks. Without this, you're reconstructing status from memory at 11pm — which is exactly the trap you're trying to leave.

How they'll know it's real: Monday 8am: you open one tab, see all active jobs, and the bookkeeper sees the same thing without asking you.

Because you said: Buyer Outcome · Stakeholders · Buyer

2. Your buyer-support agent — automated replies to homeowner inquiries

An AI assistant (something like a tuned ChatGPT or a tool like a smart email auto-responder) that, when a lead comes in via Instagram DM or email, sends a same-hour reply: thanks them, asks the 5 site questions (sun, soil, drainage, budget range, timeline), and books them onto your assessment calendar. You review and approve drafts until you trust it, then let it send directly.

Why this matters: You're losing 40% of leads to faster competitors and quote turnaround is 11 days. The bottleneck isn't the quote — it's that homeowners feel forgotten in the first 24 hours. This kills that. Applies strongly to you.

How they'll know it's real: Inbound lead → reply within 1 hour without you touching it; assessment booked within 48 hours.

Because you said: Catalyst · Stakeholders · Buyer Outcome

3. Your strategic-partner agent — an AI that helps you think through the business

A weekly 20-minute conversation with an AI (ChatGPT or Claude works) where you paste in last week's numbers and it asks the questions your departed designer used to surface — what's drifting, what to push on, what to drop. Not a chatbot; a thinking partner with memory of your situation.

Why this matters: You decide everything alone and admin drains you fast. You don't need another tool; you need a second brain that doesn't quit in March. This becomes more valuable as you grow toward three locations.

How they'll know it's real: You leave the Sunday review with three clear decisions for the week, not a longer to-do list.

Because you said: Buyer · Catalyst · North Star

4. Engagement orchestration — automatic follow-ups with homeowners

After assessment, the system sends the quote within 48 hours, then follow-ups at day 3, day 7, day 14 if no answer — and a 'one-year warranty check-in' email at month 11. This is a basic email-sequence tool (Mailchimp, ConvertKit) that fires off your pipeline stages.

Why this matters: 11-day quote turnaround means most leads have already hired someone else. Even when you win, the warranty check-in protects your bedrock reputation for horticultural judgment.

How they'll know it's real: No homeowner waits more than 48 hours after assessment without hearing from you.

Because you said: Catalyst · Stakeholders · North Star

5. Currency pipeline — the plant-knowledge library that replaces the departed designer's brain

A structured plant-spec document (Notion page or even a well-organized Google Doc) that captures: for each plant you install, what site conditions it needs (sun/soil/water/zone), what it costs, what it pairs with, and the warranty risk. Built once over 2-3 weekends from what's in your head and your crew lead's, then added to whenever a new plant gets specced.

Why this matters: This is the single most load-bearing item for spring. The designer left with the institutional memory; the crew is now eating warranty redos because they're guessing. This is what makes scoping repeatable by anyone on staff — exactly Outcome #1.

How they'll know it's real: Crew lead can pull a site-appropriate plant list for a new job without calling you.

Because you said: Catalyst · Buyer Outcome · Stakeholders · Identity

6. Library governance — the rule for who updates the plant database and when

One sentence written down: 'Crew lead adds a new plant entry the first time we spec it; owner reviews monthly.' That's the whole governance layer. The point is it doesn't decay back into one person's head.

Why this matters: You just lived through what happens when knowledge sits in one brain that walks out the door. The rule is cheap; the absence is catastrophic.

How they'll know it's real: Three months from now, the plant library has entries you didn't personally write.

Because you said: Catalyst · Buyer Outcome · North Star

7. Knowledge propagation — making sure the crew actually uses the plant spec sheet

Every job gets a printed (or phone-viewable) site→plant spec sheet handed to the crew lead before install. Not 'it's in the database' — physically in their hand. This is a 10-minute step in your pipeline, not a tool.

Why this matters: Crew is installing wrong plants for sites today. The library only matters if it reaches the field. Without this step, you've built a binder nobody reads.

How they'll know it's real: Warranty replacement rate drops over a season; crew lead stops calling you mid-install with plant questions.

Because you said: Catalyst · Stakeholders

8. The outcome-tool-context graph — knowing which tool serves which goal

A one-page map showing: this tool serves this outcome. Square = retail sales (don't touch). Pipeline board = project visibility. Plant library = scoping. Email sequence = follow-up. So when you're tempted to add a 5th tool, you can see whether you need it or whether it duplicates something.

Why this matters: You said the word 'integration' makes you anxious and daily fiddling = abandonment. This map is the antidote to tool sprawl — the thing that quietly kills small businesses that try to modernize.

How they'll know it's real: When a vendor pitches you software, you can say 'no, that overlaps with X' in under 30 seconds.

Because you said: Constraints · Buyer

9. Recommendation pipeline — automated next-best-plant or next-best-action suggestions

N/A for you right now. This would be a system that, given a site assessment, recommends the plant palette automatically. You don't need it yet — your plant library plus crew-lead judgment will do the job for spring. Revisit when you hit location #3 and the library has 200+ plants in it.

Why this matters: Saying 'not yet' protects your $200/mo budget and your energy. The simpler library does 90% of the work.

How they'll know it's real: N/A

Because you said: Constraints · North Star

10. The alarm — the one number that screams when something's wrong

A single weekly metric you watch: 'days from lead to quote sent.' If it crosses 3 days, something's broken — the assistant isn't replying, assessments aren't getting booked, or you're the bottleneck. This is a cell in your pipeline sheet that turns red.

Why this matters: 11-day turnaround is what nearly killed your season. You need a tripwire that catches it at day 3, not day 11. One number, not a dashboard.

How they'll know it's real: The week the number goes red, you know it on Monday — not when leads stop coming in three weeks later.

Because you said: Catalyst · Buyer Outcome

11. Profit + stage tracking — knowing per-job margin before you bid the next one

The bookkeeper logs actual cost (plants + crew hours + warranty replacements) against each job's quoted price, in the same pipeline view. You see margin per job, not just revenue. Quickbooks plus a shared sheet does this; no new tool needed.

Why this matters: You're personally guaranteed on both leases. Eating warranty redos invisibly is how a $22k job becomes a $4k job. The bookkeeper today reconstructs this after the fact — should be live.

How they'll know it's real: You can name your worst-margin job type from last month without doing math.

Because you said: Buyer · Stakeholders · Constraints

12. Weekly rhythm — the Monday review and the Friday adjustment

Two recurring 20-minute slots: Monday 8am you scan the pipeline + the alarm number. Friday 4pm you adjust — move one thing, decide one thing, drop one thing. Calendar reminders, not software. This is the heartbeat that keeps everything else from drifting.

Why this matters: You explicitly asked for 'a weekly rhythm so every Monday I know every project's stage.' Without this, the tools become shelfware. With it, 4 hrs/wk of admin is enough.

How they'll know it's real: Family stops watching you quote at 11pm because Friday-4pm-you already handled it.

Because you said: Buyer Outcome · Constraints · Stakeholders

13. Tribe surface — a community of peer operators

N/A for you right now. This would matter if you had a network of other independent garden-center owners to share plant-library entries and warranty data with. You're a solo owner focused on surviving spring; community comes after stability. Worth revisiting when you're opening location #3 and want benchmarks.

Why this matters: Being honest: you don't have 4 hrs/wk of admin AND time for a peer group right now. Don't pretend otherwise.

How they'll know it's real: N/A

Because you said: Buyer · Constraints · North Star

Turning your answers into the live picture your system uses

The answers you gave — 19 staff, two locations, $3k–$22k design-install jobs, a one-year planting guarantee, spring is 60% of revenue, you have 4 admin hours in season, your crew lead and bookkeeper are your bench — become the standing facts every other routine refers to. When something about Rooted changes (a new crew member, a new price band, a second designer eventually), you update this picture and everything downstream adjusts.

Why this matters: You decide everything alone and admin lives in the cracks. If the system doesn't already know your constraints, every routine will ask you to re-explain them and you'll abandon it.

How they'll know it's real: When you describe a change in one place (e.g. 'crew lead now does assessments solo') and the next Monday view, the quote template, and the spec sheet all reflect it without you re-entering it three times.

Because you said: Identity · Buyer · Constraints

How the next move gets recommended to you each week

Given that spring starts in 6 weeks and the bleeding points are quote turnaround (11 days → must be 2) and plant-spec accuracy (warranty redos), the system surfaces one next move at a time aimed at those two numbers — not a backlog of 30 ideas. Off-season it shifts to training the crew lead and building the assessment script library.

Why this matters: You said numbers/admin drain you fast and daily fiddling means you abandon things. One recommended move respects that.

How they'll know it's real: You open the system on Monday and see one thing to decide, not a dashboard.

Because you said: Catalyst · Constraints · Buyer Outcome

Re-running the plan when something real changes

Triggered by events you'll actually have: crew lead off sick, a $22k job lands, a supplier can't deliver a spec'd plant, quote turnaround creeps past 3 days. The system re-checks priorities against your spring deadline and tells you what to drop or shift. You're not redoing the whole plan — you're locking what's still true and adjusting what isn't.

Why this matters: Both leases are personally guaranteed and you lose the season if scoping breaks. You need a routine that handles disruption without requiring you to rebuild from scratch at 11pm.

How they'll know it's real: A disruption hits and within one sitting you know what's still on and what's paused.

Because you said: Catalyst · Buyer · North Star

Keeping your 2–3 chosen tools healthy

N/A as an ongoing workflow for you right now — your budget is ~$200/mo and ~$500 one-time, and the deliverable is explicitly 2–3 tools chosen and set up, not a pool to maintain. Revisit only if you add a third location or hire a replacement designer.

Because you said: Buyer Outcome · Constraints

Questions you raise from the floor or the field

When a homeowner asks something the assessment script doesn't cover, or the crew lead hits a plant-site combination he's unsure about, that question goes into one place and becomes either a new line in the assessment script or a new entry in the plant-spec reference. Your field reality keeps feeding the system instead of dying in a text thread.

Why this matters: The institutional memory walked out in March. The only way to rebuild it without another single point of failure is to capture what's learned during the season as it happens.

How they'll know it's real: The assessment script and spec sheet get longer and sharper across the season without you setting aside time to write them.

Because you said: Catalyst · Stakeholders · Buyer Outcome

Building and maintaining your plant-spec reference

The horticultural-judgment library — what plant for what soil/light/water, what fails where, what's under warranty risk — is the asset the departed designer walked away with. This routine is how it gets rebuilt: every completed install and every warranty replacement adds one row. Your crew lead can be trained to do the entries; you review.

Why this matters: Your bedrock is trusted horticultural-judgment reputation. Without this library, every new hire restarts from zero and you stay the bottleneck forever.

How they'll know it's real: A new staff member can spec a site correctly by looking things up, not by interrupting you.

Because you said: Identity · Catalyst · Stakeholders · North Star

Getting what one person learns into everyone else's hands

When the crew lead learns a soil pattern in West Asheville, or a retail-floor staffer hears the same homeowner question three times, that knowledge moves to the assessment script, the quote template, or the spec sheet — so the next person doesn't relearn it. With 19 staff across two locations, this is how the team stays one team.

Why this matters: You're the only person who talks to both locations and the crew lead. Without this, you remain the human integration layer and you can't get to three locations.

How they'll know it's real: Both locations quote the same way for the same site type without you brokering it.

Because you said: Identity · Buyer · North Star

Keeping the customer-facing voice consistent

N/A as a standalone workflow for you right now. Your voice with homeowners is carried by the guided-assessment conversation itself, not by content output. When you have a marketing function or a second designer drafting proposals, this comes back on.

Because you said: Identity · Constraints

Catching trouble before spring gets away from you

A small set of numbers gets watched: days from lead to quote (target 2, alarm at 4), % of installs with a warranty replacement, % of design leads lost to a faster competitor, and weekly admin hours you actually spent. If one trips, the Monday view flags it and you get a recommended move (see the weekly recommendation routine), not a wall of charts.

Why this matters: You said you lose ~40% of leads to faster competitors and you're 6 weeks from the season that is 60% of revenue. You need the early warning, not the post-mortem.

How they'll know it's real: You learn quote turnaround is slipping on the Monday it slips, not in April when bookings are down.

Because you said: Catalyst · Constraints · Stakeholders

Your Monday rhythm and where the money is

Every Monday: every active project's stage (lead / assessment booked / quoted / scheduled / installed / in warranty window), the quotes outstanding past 2 days, and the bookkeeper's live view of job costs against quote. One sitting, in your admin window, not at 11pm. The bookkeeper sees the same view so she stops reconstructing after the fact.

Why this matters: You explicitly asked for this: 'every Monday I know every project's stage.' It's also the routine that gets your evenings back and lets the bookkeeper do her job in real time.

How they'll know it's real: Monday morning you can name every open project's stage in under 15 minutes; the bookkeeper hasn't had to call you to ask what stage something is in.

Because you said: Buyer Outcome · Stakeholders · Constraints

A digest for the people around you

N/A for now. You don't have a peer group or community to digest to, and your stakeholders (homeowners, crew lead, bookkeeper, family) are each handled by a specific routine above. Revisit when you're mentoring a second designer or running three locations.

Because you said: Stakeholders · North Star

Moving something from 'we're trying it' to 'this is how we do it'

When a new assessment script, a new quote template, or a new spec-sheet section has worked for a few jobs, this is the routine that promotes it from your draft into what every staffer is expected to use — and retires the old version so nobody's working from two playbooks. You decide; the crew lead and floor staff get the updated version.

Why this matters: You decide alone and you can't afford two versions of 'how we quote' floating around in spring. This is also how the system eventually runs without you — promoted practices, not tribal knowledge.

How they'll know it's real: When you ask any staff member how a site assessment is done, you get the same answer.

Because you said: Buyer · Identity · North Star

Where you stand

Your scoping designer left in March and took the plant knowledge with her. Quote turnaround has gone from 2 days to 11, you're losing roughly 40% of design leads to faster competitors, and the crew is installing wrong plants for sites and eating warranty replacements. Spring — 60% of your revenue — starts in 6 weeks, with both location leases personally guaranteed and you working ~55 hrs/wk on the floor with admin squeezed into ~4 hrs/wk.

Why this matters: This is the honest read a board would need before hearing any plan. The clock, the leak, and the personal exposure are all real and named.

How they'll know it's real: Quote turnaround time and design-lead win rate — both are measurable today and both moved in the wrong direction after March.

Because you said: Catalyst · Buyer · Constraints

What your system is, in one paragraph

Rooted runs on a repeatable lead → site-assessment → quote → plant-spec process that any trained staff member can execute, supported by 2–3 simple tools that don't break Square, with a Monday rhythm where every active project's stage is visible at a glance — so horticultural judgment becomes the company's asset, not one person's memory.

Why this matters: This is the sentence you can repeat verbatim to a banker, a new hire, or your crew lead and have them understand what Rooted actually is now.

How they'll know it's real: Anyone on staff — not just you — can take a new lead from first call to signed quote without escalating to your brain.

Because you said: Identity · Buyer Outcome · North Star

What's working, what's drifting, what needs you

Working: the retail floor, your reputation for co-designed installs and the 1-year planting guarantee, the crew lead you can train, and the bookkeeper already in place. Drifting: quote turnaround (2 → 11 days), design-lead conversion (~40% lost), plant-spec accuracy (warranty redos), and your evenings (quoting at 11pm). Needs you personally: the decision on the 2–3 tools, training the crew lead on the assessment-and-spec process, and holding the Monday review until it's a habit.

Why this matters: It separates what to protect, what to repair before spring, and what only you can do — so you stop spending your 4 admin hours on the wrong things.

How they'll know it's real: By week 3 the 'drifting' column should be shrinking weekly, not staying the same.

Because you said: Identity · Catalyst · Constraints · Stakeholders

The load-bearing capability

The one thing that cannot erode is Rooted's trusted horticultural judgment — specifically, the site-assessment-to-plant-spec step. If that becomes guesswork, every other piece (quote speed, warranty cost, referrals, the five-year plan of being the name homeowners are referred to) collapses. Tools and rhythms exist to protect this one capability; they are not the point.

Why this matters: Your bedrock is reputation for judgment, not transaction volume. Naming the load-bearing piece keeps you from optimizing the wrong thing when spring pressure hits.

How they'll know it's real: Warranty replacement rate on installs. If it stays low after the designer's departure, the judgment has successfully moved into the system.

Because you said: Identity · North Star

The 60–90 day proof

By the end of spring you'll know it's working if: quote turnaround is back under 2 days, design-lead win rate is recovering toward pre-March levels, the crew lead is producing site→plant-spec sheets without you, warranty-replacement incidents are flat or down versus last spring, every Monday you can name the stage of every active project in under 15 minutes, and you are not quoting after dinner. These are the numbers and observable states — not a feeling that things are calmer.

Why this matters: These are your own success terms from the intake, made concrete enough that you can't fool yourself in week 8 when you're tired.

How they'll know it's real: All six measures reviewed in the Monday rhythm; any one of them off-track for two weeks running is a flag.

Because you said: Buyer Outcome · Catalyst · Stakeholders

The one risk that kills this

The sharpest failure mode is you treating the new system as daily admin and abandoning it — because numbers and fiddling drain you fast, season is 55-hr weeks, and admin lives in the cracks. If the Monday rhythm slips and tool setup leaks into evenings, you'll quietly revert to quoting from your head at 11pm and the design lead leak continues. Mitigation: the system is sized to 4 admin hrs/wk in-season, tools are chosen for you (not researched by you), the crew lead owns the assessment sheet, and the bookkeeper owns project-stage visibility — your only standing job is the Monday review.

Why this matters: Naming the failure mode honestly is what makes the mitigation real. The risk isn't competitors — it's the design quietly being dropped because it costs you energy you don't have.

How they'll know it's real: Two consecutive missed Monday reviews = intervene immediately; that's the leading indicator of reversion.

Because you said: Buyer · Constraints

What you show the board

Sentence one: 'When our designer left, quote turnaround went from 2 to 11 days and we were losing about 40% of design leads — so we moved the scoping and plant-spec knowledge out of one person's head and into a process the team runs.' Sentence two: 'Homeowners now get a guided site assessment and quote within 2 days, the crew lead works from a clear plant-spec sheet so we stop eating warranty redos, and the bookkeeper sees project stages live instead of reconstructing them later.' Sentence three: 'That's the same system that gets Rooted to three locations booked a season ahead — because it's built on horticultural judgment we can train, not on me being in the field 55 hours a week.'

Why this matters: These are the three sentences that align homeowners, your crew lead, your bookkeeper, your family, and any future lender or partner on the same story.

How they'll know it's real: You can say all three out loud without hedging or adding caveats.

Because you said: Stakeholders · North Star · Catalyst

Week 1 — Build the site-assessment intake form

WHY: This is the front door of outcome #1 (the lead→assessment→quote→spec system) and the single biggest reason quotes went from 2 days to 11 — there's no structured way to capture what the designer used to hold in her head. WHERE: A free Google Form (no Square risk, no developer, works on your phone in the field). WHAT: (1) List every question the departed designer asked on a site visit — soil, light hours, drainage, slope, existing plants, deer pressure, homeowner's must-haves, budget band, photos. (2) Build those as a Google Form with required fields and a photo-upload question. (3) Add a budget-band dropdown ($3k–7k, $7k–12k, $12k–22k) so leads self-sort. (4) Test it on your own house this week. GOTCHAS: You will be tempted to make it short to seem friendly — don't. The form IS the horticultural judgment now. Recovery: if a field feels too long, mark it 'internal only' and you fill it on-site, not the homeowner. VERIFICATION: You walk one real site this week with only the form (no notebook) and produce a complete intake without calling anyone for help. Success signal: the crew lead could read that intake and know what the site is.

Why this matters: Without this, nothing else in the four weeks works — every other tool depends on a structured intake.

How they'll know it's real: One real site walked using only the form, complete intake produced.

Because you said: Catalyst · Buyer Outcome · Buyer · Constraints

Week 1 — Build the plant-spec decision sheet

WHY: Directly addresses the crew-installing-wrong-plants problem from your catalyst and the warranty-replacement bleed — and it's what your crew lead needs to stop guessing. WHERE: A single Google Sheet, one tab, that maps site conditions → approved plant choices. WHAT: (1) Columns: sun level, soil type, moisture, deer pressure, mature size band. (2) Rows: every plant you actually install regularly (start with your top 40 — not your whole catalog). (3) For each plant, fill the conditions where it survives your 1-year guarantee. (4) Add a 'do not spec if' column for the deal-breakers. (5) Have your crew lead review it and add the plants he's seen fail. GOTCHAS: You'll want to include every plant on the retail floor. Don't — this is the install spec sheet, not inventory. Plants you wouldn't guarantee for a year don't belong on it. VERIFICATION: Filter the sheet by 'full shade, clay, deer pressure' and you get a usable shortlist in under 30 seconds. Success signal: crew lead says 'yes, I'd plant from this list.'

Why this matters: This sheet IS the horticultural judgment you sell — externalized so it doesn't walk out the door again.

How they'll know it's real: Crew lead endorses the list; filtering produces a usable shortlist in under 30 seconds.

Because you said: Identity · Catalyst · Buyer Outcome · Stakeholders

Week 1 — Stand up the project-stage board

WHY: Outcome #3 says every Monday you need to know every project's stage. This board is where that lives, and it's what the bookkeeper will read live instead of reconstructing later. WHERE: Trello (free tier) or a Google Sheet kanban — pick whichever you'll actually open. Trello is more visual; the Sheet is closer to what you know. WHAT: (1) Six columns: New Lead → Assessment Booked → Assessment Done → Quote Sent → Won/Scheduled → Installed. (2) One card per project, with the homeowner name, budget band, and a link to their intake form response. (3) Move cards as reality changes — that's the only rule. GOTCHAS: You'll create more columns because reality is messier. Resist for now. Six columns or you'll stop updating it. Recovery: if a project doesn't fit, it stays in the closest column with a note. VERIFICATION: At end of Week 1, every lead from the last two weeks is on the board in the right column. Success signal: you can answer 'what's the status of the Johnson project?' in 5 seconds without calling anyone.

Why this matters: This is the single artifact that gives you Monday visibility and gives the bookkeeper live data.

How they'll know it's real: Every current lead is on the board; status questions answered in 5 seconds.

Because you said: Buyer Outcome · Stakeholders

Week 2 — Run your first three leads fully through the system

WHY: Tools that aren't used by Friday won't be used in spring. This is where outcome #1 gets verified by actually USING it on real money. WHERE: Next three design leads that come in — phone, Instagram DM, or walk-in. WHAT: (1) Every lead gets the Google Form link by text within 1 hour of first contact. (2) You or crew lead does the site assessment using the form on phone. (3) Plant choices come from the spec sheet — write them on the quote, not from memory. (4) Card moves through the board as each step happens. (5) Quote goes out within 2 business days of the assessment. GOTCHAS: The first lead will feel slower than your old way because the system is new. That's normal — by lead three it's faster. Don't bail back to the old way. Recovery: if you catch yourself quoting from memory, stop and pull up the spec sheet, even mid-call. VERIFICATION: Three leads, three completed intakes, three quotes sent within 2 days each. Success signal: quote turnaround back to your old 2-day mark on at least 2 of 3.

Why this matters: This is the proof the system works before spring volume arrives — and the first revenue it touches.

How they'll know it's real: Three leads through, quote turnaround at 2 days on at least 2 of 3.

Because you said: Catalyst · Buyer Outcome · Stakeholders

Week 2 — Train your crew lead on the spec sheet

WHY: Your F4 says you're the only person talking to both locations and the crew — that's the bottleneck. Your F7 says in 5 years the team runs this. Training starts now, not later. WHERE: One 90-minute session on a slow morning, at the install yard with the sheet open on a laptop or tablet. WHAT: (1) Walk him through every column and what each condition means in his words. (2) Pull up the last 3 warranty-replacement jobs and have him use the sheet to pick what should have gone in instead. (3) Give him edit access so he can add field notes when a plant fails. (4) Agree he uses it on every job starting next week — no exceptions. GOTCHAS: He may say he 'already knows.' He probably does for some plants — but the point is the sheet captures it so the next hire doesn't need 10 years. Frame it as 'help me capture your judgment,' not 'replace yours.' VERIFICATION: He independently specs the next install from the sheet without calling you. Success signal: zero warranty calls on jobs he specs from the sheet in the next 30 days.

Why this matters: Transfers the bottleneck off you and starts building the trained team your 5-year picture requires.

How they'll know it's real: Crew lead specs a job independently from the sheet.

Because you said: Buyer · Stakeholders · North Star

Week 3 — Connect the intake form to the project board

WHY: Right now you're copying lead info from the form into the board by hand — that's the kind of admin friction that makes you abandon systems. Automating this one link saves ~30 min/week and removes a daily-fiddling failure mode. WHERE: Google Forms → board, using the form's built-in 'send to sheet' (no integration tools, no Zapier needed for this one). WHAT: (1) In the Google Form, turn on 'responses to Google Sheet.' (2) Add one column to that sheet: 'board card created? Y/N.' (3) Once a day (Monday during your admin block), open the sheet, create a Trello card or board row for any new responses, mark Y. (4) That's it — no auto-magic, just one place to scan once a day. GOTCHAS: You'll be tempted to make this fully automatic with Zapier. Don't — your F5 says 'integration' makes you anxious and you'll abandon a system that breaks silently. A manual Monday scan you understand beats automation you don't trust. VERIFICATION: Open the responses sheet on Monday — every row marked Y or you create the missing card. Success signal: zero leads get lost between form and board.

Why this matters: Removes the highest-friction admin step without crossing your no-integration-anxiety line.

How they'll know it's real: Zero leads lost between form and board for two weeks running.

Because you said: Buyer Outcome · Constraints

Week 3 — Run the install workflow end-to-end on one job

WHY: Weeks 1–2 proved the front-end (lead → quote). This proves the back-end (quote → install → warranty), which is where the warranty-replacement bleed lives. WHERE: Pick one Won/Scheduled project this week. WHAT: (1) Crew lead pulls the plant spec from the sheet, prints it, brings it to site. (2) On install day, he marks any deviations directly on the printout (substitutions, count changes). (3) Photo of the marked-up printout goes back into the project card. (4) Bookkeeper sees the card move to Installed and can reconcile costs same-week, not month-end. GOTCHAS: A plant will be out of stock and he'll substitute on the fly — that's fine, but the substitution MUST be from the spec sheet's same-conditions row, not 'this looks close.' VERIFICATION: Job installs with marked-up spec sheet in the card, bookkeeper reconciles within 5 days. Success signal: bookkeeper says 'I didn't have to ask anyone what got planted.'

Why this matters: Closes the loop from lead all the way to reconciled job — the full system, end to end.

How they'll know it's real: Bookkeeper reconciles without asking anyone what was planted.

Because you said: Catalyst · Stakeholders

Week 3 — Re-open and fix whichever piece didn't match reality

WHY: After two weeks of real use, one of the three tools (form, spec sheet, or board) is fighting you. Fix it now, before spring, while the cost of change is low. WHERE: Whichever tool the crew lead or you complained about most. WHAT: (1) List every moment in the last two weeks you bypassed the system or felt friction. (2) Pick the top 3 issues. (3) For each, decide: add a field, remove a field, or change wording. (4) Make the changes in one sitting, not over a week. (5) Tell crew lead what changed in one text. GOTCHAS: The temptation is to rebuild everything. Don't — change only what actively broke. Anything that 'could be better' but isn't blocking, leave alone. VERIFICATION: Week 4 runs without you noticing the tool — that's the bar. Success signal: you go a full week without thinking about the tools themselves, only the work.

Why this matters: Catches the real-world mismatches before spring volume makes them expensive.

How they'll know it's real: Week 4 passes without you noticing the tools — they just work.

Because you said: Buyer · Constraints

Week 4 — Establish the Monday 20-minute review

WHY: Outcome #3 explicitly: every Monday you know every project's stage. This is the cadence that makes it real and keeps admin inside your 4 hrs/week in-season budget. WHERE: 20 minutes, Monday morning before the floor opens, coffee in hand, board open. WHAT: (1) Scan board left to right. (2) Any card that hasn't moved in 7 days gets a note: why stuck, what unsticks it. (3) Any New Lead older than 48 hours — call today. (4) Any Quote Sent older than 7 days — follow up today. (5) Forward the snapshot to the bookkeeper. GOTCHAS: It will creep to 45 minutes. Set a timer for 20. If something needs more, it becomes a separate scheduled block, not an extension. VERIFICATION: Four consecutive Mondays done in under 25 minutes each. Success signal: by week 4, no card is older than 7 days in any active column.

Why this matters: This is the rhythm that replaces 11pm-quoting and gives your evenings back.

How they'll know it's real: Four consecutive Mondays under 25 minutes; no card aging past 7 days.

Because you said: Buyer Outcome · Constraints · Stakeholders

Week 4 — Activate the lead-triage decision rule

WHY: Spring means more leads than you can quote in 2 days. You need a rule that decides which leads get the fast lane, not your gut at 11pm. This protects the 'horticultural judgment, not most transactions' bedrock from your North Star. WHERE: A one-page printout taped inside the cash wrap at both locations and pinned to the board. WHAT: (1) Rule: budget band $7k+ AND complete intake form returned within 48 hrs → fast lane (assessment booked within 3 days). (2) Budget band under $7k OR incomplete intake → standard lane (assessment within 10 days). (3) No budget given → you call once to ask, then it goes standard. (4) Crew lead and floor staff can apply this without asking you. GOTCHAS: You will want to make exceptions for nice people. Don't — exceptions are how you ended up at 11 days. The rule frees you; exceptions re-trap you. VERIFICATION: One week of leads triaged by floor staff without escalation to you. Success signal: you stop being the routing bottleneck for incoming leads.

Why this matters: Turns 'I decide everything alone' (F4) into 'the rule decides, I'm only consulted on edge cases.'

How they'll know it's real: A full week of leads triaged without escalation to you.

Because you said: Identity · Buyer · North Star

Week 4 — Schedule the 90-day checkpoint

WHY: Spring will stress-test everything. You need a scheduled stop to look at what bent, before it becomes how-we-do-things. WHERE: Calendar — a 2-hour block, 90 days from this Friday, ideally on an off-day. WHAT: (1) Put it on the calendar now, before spring buries you. (2) Title it 'Rooted system review — what bent.' (3) Three questions to answer that day: which tool stopped getting used, where did leads still slip, where am I still the only one who can do something. (4) Bring the board, the form responses, and the spec sheet edit history. GOTCHAS: You will want to move it when spring is busy. Don't — that's exactly when you need it. Move other things; this one is the appointment with your business. VERIFICATION: Block exists on the calendar before end of Week 4. Success signal: you actually take the block in 90 days and act on at least one of the three questions.

Why this matters: This is how the four-week setup becomes a 5-year system instead of a spring patch job.

How they'll know it's real: Block on calendar by end of week 4; honored 90 days from now.

Because you said: Catalyst · North Star