| Document | Status | What it gave up |
|---|---|---|
| Strategic Foundation | Read | PREVIEW-strategic-foundation_5.html. 0 sections, the engagement and the fee. |
| Proposal | Read | preview-proposal_9.html. 15 sections, the engagement and the fee. |
| Internal analysis | Read | preview-internal-report_2.html. 76 question and answer pairs, 22 sections. |
| Client diagnosis | Read | preview-client-diagnosis_3.html. 16 profile fields, 16 sections. |
Every field in the brief carries a provenance mark. 12 of 67 came directly from the discovery record. 38 were inferred from what was said and must be read before sign-off. 0 came from live sources and carry a citation. 17 could not be established at all.
No field was invented. Anything the record did not support was left outstanding, and it prints as outstanding on the client-facing brief rather than being covered with a plausible sentence.
| Section | Field |
|---|---|
| 04 · Domain + WorkspaceNeeds input | Domain + DNS · configuration |
| 08 · Scheduling + PMNeeds input | Scheduling · configuration |
| 08 · Scheduling + PMNeeds input | Project management · configuration |
| 11 · SOP LibraryNeeds input | SOP 03 · name |
| 11 · SOP LibraryNeeds input | SOP 03 · purpose |
| 11 · SOP LibraryNeeds input | SOP 03 · trigger and owner |
| 11 · SOP LibraryNeeds input | SOP 03 · steps |
| 11 · SOP LibraryNeeds input | SOP 03 · output and exceptions |
| 13 · Security + AccessNeeds input | Recovery protocol |
| 16 · Review & AcceptanceNeeds input | Review window |
| 16 · Review & AcceptanceNeeds input | Review window · note |
| 16 · Review & AcceptanceNeeds input | All credentials |
| 16 · Review & AcceptanceNeeds input | Credentials · note |
| 16 · Review & AcceptanceNeeds input | Revisions |
| 16 · Review & AcceptanceNeeds input | Revisions · note |
| 16 · Review & AcceptanceNeeds input | Next gate |
| 16 · Review & AcceptanceNeeds input | Next gate · note |
| Section | Field |
|---|---|
| 01 · Stack SynthesisModeled | The operating stack, in one sentence |
| 01 · Stack SynthesisModeled | 02 · Who operates it |
| 01 · Stack SynthesisModeled | 03 · What feeds Week 03 |
| 02 · Stack ArchitectureModeled | Layer 01 · CAPTURE |
| 02 · Stack ArchitectureModeled | Layer 02 · ROUTE |
| 02 · Stack ArchitectureModeled | Layer 03 · SCHEDULE |
| 02 · Stack ArchitectureModeled | Layer 04 · EXECUTE |
| 05 · HubSpot CRM ConfigurationModeled | Pipeline stages |
| 05 · HubSpot CRM ConfigurationModeled | Custom properties and lifecycle |
| 06 · Forms + TrackingModeled | Discovery form |
| 06 · Forms + TrackingModeled | Contact form |
| 06 · Forms + TrackingModeled | Tracking pixel |
| 06 · Forms + TrackingModeled | Attribution model |
| 07 · Lead-Capture FlowModeled | The loop |
| 09 · Operating CadenceModeled | Operating manual · overview |
| 09 · Operating CadenceModeled | Meeting and review cadence |
| 09 · Operating CadenceModeled | How decisions are recorded |
| 09 · Operating CadenceModeled | SOP 01 · name |
| 09 · Operating CadenceModeled | SOP 01 · overview |
| 09 · Operating CadenceModeled | SOP 02 · name |
| 09 · Operating CadenceModeled | SOP 02 · overview |
| 09 · Operating CadenceModeled | SOP 03 · name |
| 09 · Operating CadenceModeled | SOP 03 · overview |
| 10 · Decision Rights MatrixModeled | Decisions |
| 11 · SOP LibraryModeled | SOP 01 · name |
| 11 · SOP LibraryModeled | SOP 01 · purpose |
| 11 · SOP LibraryModeled | SOP 01 · trigger and owner |
| 11 · SOP LibraryModeled | SOP 01 · steps |
| 11 · SOP LibraryModeled | SOP 01 · output and exceptions |
| 11 · SOP LibraryModeled | SOP 02 · name |
| 11 · SOP LibraryModeled | SOP 02 · purpose |
| 11 · SOP LibraryModeled | SOP 02 · trigger and owner |
| 11 · SOP LibraryModeled | SOP 02 · steps |
| 11 · SOP LibraryModeled | SOP 02 · output and exceptions |
| 14 · Trademark (Elective)Modeled | Filing path |
| 15 · What This EnablesModeled | Week 03 · Brand & web |
| 15 · What This EnablesModeled | Week 04 · GTM & launch |
| 15 · What This EnablesModeled | Days 31-60 · Aftercare |
Nothing was looked up. The lookup was off, or every field came from the record.
| Account | Owner email | Access notes |
|---|---|---|
| Domain Registrar | test@test.com | Domain is test-domain.com. Registrar and DNS records are not entered in the operator record. |
| Google Workspace Admin | Google Workspace is the workspace platform standing under this engagement. Owner email, plan tier, and seat count are not entered in the operator record. | |
| HubSpot | test@test.com | Covers HubSpot CRM and HubSpot Forms + Pixel, both live and credentialed to this account. Plan tier and pipeline stage configuration are not entered in the operator record. |
| Calendly | test@test.com | Live and syncing bookings back to the CRM record. Event types configured are not entered in the operator record. |
| Project Mgmt Tool | test@test.com | Live. The specific tool and board configuration are not entered in the operator record. |
Ownership entered at configuration
| Account | Owner email |
|---|---|
| Domain registrar | test@test.com |
| HubSpot CRM | test@test.com |
| HubSpot Forms + Pixel | test@test.com |
| Calendly / Scheduling | test@test.com |
| Project Management | test@test.com |
Handoff. Passwords and account access transfer via secure handoff through a shared vault. No credential is sent in plain text or by email.
This section exists on the internal build sheet only. The client-facing deliverable shows these accounts as credentialed and transferred, without the owner emails or notes. No password or secret is ever recorded here.
| Foundation section | Summary |
|---|---|
| What is in this brief | Section 00 · Reading mapWhat is in this briefEvery section below is a working artifact. Together they define the brief that Weeks 2 through 4, and the engagements that follow, are built against.01Executive SummaryThe syn |
| Executive Summary | Section 01 · Executive SummaryExecutive SummaryThe synthesis, before the work that follows.North Harbor Provisions is the coastal pantry brand for households that cook from scratch on weeknights and refuse to trade prove |
| Strategic Pillars | Section 02 · Strategic PillarsStrategic PillarsThe four pillars. WHO, WHY, HOW, WHAT.Pillar 01 · WHOThe buyer the strategy is built forThe weeknight cook who has already left the supermarket for direct-from-producer buyi |
| Mission & Vision | Section 03 · Mission & VisionMission & VisionThe north star. The shortest version of what the business is for.“North Harbor Provisions exists so that buying well does not have to be a second job. The business intends to |
| Brand Positioning | Section 04 · Brand PositioningBrand PositioningWhere the business sits, and what it owns in the buyer's mind.FOR coastal households that cook from scratch, NORTH HARBOR PROVISIONS IS THE standing pantry THAT arrives from |
| Value Proposition | Section 05 · Value PropositionValue PropositionThe frame. WHO, PROBLEM, PROMISE, PROOF.WHOThe audience this is built forThe weeknight cook, already buying direct, already over-subscribed.PROBLEMWhat they are trying to so |
| Brand Promise & Differentiators | Section 06 · Brand Promise & DifferentiatorsBrand Promise & DifferentiatorsThe commitments, and why this is different.Brand promiseThe commitment to the buyerThe pantry arrives before it runs out, or the next one is free |
| Competitive Landscape | Section 07 · Competitive LandscapeCompetitive LandscapeThe category, and the gap the business fits into.CompetitorPositioningStrengthWeakness / gapThrive MarketBulk pantry, membershipScale and priceProvenance is generic. |
| Positioning Map | Section 08 · Positioning MapPositioning MapThe two by two, against the axes that matter.High provenanceQ01Single-producer subscriptionsNamed boats and named farms, and the buyer has to assemble the pantry themselves.Q02N |
| SWOT Analysis | Section 09 · SWOT AnalysisSWOT AnalysisThe honest read. Strengths, weaknesses, opportunities, threats.StrengthsInternal · favorableFounder credibility with producers. Existing relationships that a funded entrant cannot b |
| White Space | Section 10 · White SpaceWhite SpaceThe opening. Defensible, and currently un-served.There is no credible operator assembling a multi-producer coastal pantry into a single standing order with named provenance on the box.0 |
| Market Context | Section 11 · Market ContextMarket ContextThe market. Industry size, growth, phase.Industry sizeTBCOutstanding. To be completed before sign-off.Growth rateTBCOutstanding. To be completed before sign-off.Market phaseTBCOut |
| TAM · SAM · SOM | Section 12 · TAM · SAM · SOMTAM · SAM · SOMThe market sized. Total, serviceable, obtainable.TAM · Total addressableTBCOutstanding. To be completed before sign-off.SAM · Serviceable addressableTBCOutstanding. To be comple |
| Forces Shaping the Buyer | Section 13 · Forces Shaping the BuyerForces Shaping the BuyerThree forces, creating the opening right now.Force 01Subscription fatigueThe buyer has more direct food relationships than they can manage, and is now consolid |
| Trends & Catalysts | Section 14 · Trends & CatalystsTrends & CatalystsThe shifts that turn the window from open to closing.Trend 01Direct-to-consumer food normalizesA multi-year shift the business is positioned to ride rather than create.Tre |
| Risk Factors | Section 15 · Risk FactorsRisk FactorsThe risks, named, scoped, and watched.Market riskWhat could shrink the opportunityCoastal household budgets compress and the standing order becomes the first cut.Execution riskWhat co |
| Target Audience | Section 16 · Target AudienceTarget AudienceWho the business is built for. Primary and secondary, named precisely.Primary segmentThe consolidating cookWho they areCoastal Florida households, thirty-five to fifty-five, coo |
| Buyer Journey Map | Section 17 · Buyer Journey MapBuyer Journey MapThe journey, from awareness to retention.StageBuyer state of mindWhat moves them forwardWhere they areAwarenessKnows the problem of managing six subscriptions. Does not know |
| Anti-Personas | Section 18 · Anti-PersonasAnti-PersonasWho the strategy does not target, and why saying no protects the brand.Anti-persona 01The price shopperShopping the supermarket on price. They will churn for the next discount and t |
| Pricing Hypothesis | Section 19 · Pricing HypothesisPricing HypothesisThe pricing, defended against the market.Tier 01 · EntryEntry$59 / monthThe core pantry, six itemsNamed producer cardCadence set by the householdFor the buyer just trying |
| Pricing Rationale | Section 20 · Pricing RationalePricing RationaleThe math defended. Value, comparable, willingness, anchor.Value-basedWhat the outcome is worthThe buyer is paying to stop managing six relationships. The value is the attent |
| Comparable Market Anchors | Section 21 · Comparable Market AnchorsComparable Market AnchorsWhat competitors charge. Evidence, not assumption.ProviderOffer typePrice rangeWhat is includedDIY / stacking subscriptionsInternalTime and overheadSix relat |
| One-Page Brief | Section 22 · One-Page BriefOne-Page BriefThe synthesis document. Every downstream deliverable answers to it.01 · The businessA standing coastal pantry order, assembled from named producers.02 · The audienceCoastal househ |
| Hypotheses to Validate | Section 23 · Hypotheses to ValidateHypotheses to ValidateWhat the strategy bets on. The ninety-day test list.Hypothesis 01 · DemandCoastal households will pay $119 a month for a standing pantry within ninety days of laun |
| Goals & Milestones | Section 24 · Goals & MilestonesGoals & MilestonesNinety, one hundred and eighty, three hundred and sixty-five.WindowOperating goalRevenue / growth goalBrand / market goalDay 90Eight producers signed. Cadence engine live. |
| What This Enables | Section 25 · What This EnablesWhat This EnablesThe brief feeds the build, and gates without it.Week 02 · SystemsOperating stackThe pipeline stages and the lead capture ask for cadence and household size, because those ar |
| Review & Acceptance | Section 26 · Review & AcceptanceReview & AcceptanceReviewed by day twelve. Direction committed in writing.Review window5 business daysWritten feedback within the window. Silence past the window equals deemed acceptance.R |
| Prompt | What was said |
|---|---|
| Full name | Dana Whitfield |
| Company / proposed name | North Harbor Provisions |
| Title / role | Founder / Owner |
| Website | https://northharbor.co |
| Industry | Food & Beverage |
| Location | Florida, United States |
| Can you give me a brief overview of the business, and who you primarily serve? | POLISHED: Test answer 5.0 |
| Is this an existing business, something recently launched, or still in development? | Idea / pre-launch |
| What are you ultimately building toward: what does the long-term look like? | POLISHED: Test answer 7.0 |
| What prompted you to reach out at this particular point in time? | POLISHED: Test answer 8.0 |
| What does the outcome you want actually look like in practice? | POLISHED: Test answer 10.0 |
| What would success look like from your perspective once this engagement is complete? | POLISHED: Test answer 11.0 |
| If this goes well, what specifically would be different afterward? | POLISHED: Test answer 12.0 |
| Why is this the priority right now? | POLISHED: Test answer 13.0 |
| Which areas of support are in play? | Brand Strategy & Positioning, Digital Marketing & Advertising, Data Analytics & Performance |
| Out of those, which one or two feel most urgent right now? | POLISHED: Test answer 16.0 |
| How would you describe the brand today? | POLISHED: Value 17.0 |
| New, evolving, or established and needing refinement? | POLISHED: Value 17.1 |
| Clarity, consistency, credibility, memorability, or differentiation? | POLISHED: Value 17.2 |
| Strategy only, or naming, messaging, and design too? | POLISHED: Value 17.3 |
| Additional notes | POLISHED: Test answer 17.0 |
| What are you trying to grow: awareness, traffic, leads, sales, or ROI? | POLISHED: Value 18.0 |
| Which channels are in use, and what is under-performing? | POLISHED: Value 18.1 |
| What assets exist: content, creative, targeting, landing pages, flows? | POLISHED: Value 18.2 |
| Strategy, execution capacity, conversion, or reporting? | POLISHED: Value 18.3 |
| Additional notes | POLISHED: Test answer 18.0 |
| What decisions do you need better data to support? | POLISHED: Value 19.0 |
| What are you measuring now, and where is visibility lacking? | POLISHED: Value 19.1 |
| Data quality, reporting, dashboarding, attribution, or KPI selection? | POLISHED: Value 19.2 |
| Which platforms hold the data? Who uses the output? | POLISHED: Value 19.3 |
| Additional notes | POLISHED: Test answer 19.0 |
| Are you mainly looking for strategy, hands-on execution, a review of existing work, or a combination? | Strategy |
| Is the priority to build something new, improve something existing, fix a specific problem, or validate a direction? | Build something new |
| Based on your experience so far, where do you feel things are breaking down? | POLISHED: Test answer 23.0 |
| Is the issue more about lack of clarity, lack of execution capacity, underperformance, or something else? | Lack of clarity |
| If we only addressed one thing first, what would have the most impact? | POLISHED: Test answer 25.0 |
| What does the situation look like today, and what do you already have in place we should review or build on? | POLISHED: Test answer 27.0 |
| Have you worked with another consultant, agency, or advisor on this before, and what came of it? | POLISHED: Test answer 28.0 |
| Is there anything you definitely do not want to start over on? | POLISHED: Test answer 29.0 |
| Are you looking for a defined one-time project, a phased engagement, or something ongoing? | A defined one-time project |
| What would you want to have in hand by the end of this engagement? | POLISHED: Test answer 32.0 |
| Are there specific deliverables you already know you need? | POLISHED: Test answer 33.0 |
| Is there anything that should be considered out of scope from the start? | POLISHED: Test answer 34.0 |
| What would you need to provide for this to move smoothly: access, materials, inputs? | POLISHED: Test answer 36.0 |
| Are there internal approvals, stakeholder limits, or access requirements we should know early? | POLISHED: Test answer 37.0 |
| Are there internal decisions that need to happen before work could begin? | POLISHED: Test answer 38.0 |
| What timeline are we targeting? | As soon as possible |
| Is there a hard deadline, launch, event, or filing we need to build around? | POLISHED: Test answer 41.0 |
| How urgent is this from your side right now? | Critical |
| When would you ideally want work to begin? | POLISHED: Test answer 43.0 |
| What budget range are we working within? | Under $2,000 |
| Is that figure for the full initiative, or an initial phase? | The full initiative |
| Is the priority to stay within a set budget, or to solve it properly and then align scope? | Stay within a set budget |
| Are there third-party costs to account for: media spend, filing fees, software, printing? | POLISHED: Test answer 48.0 |
| Roughly, current monthly revenue? A number, or “pre-revenue.” | POLISHED: Test answer 50.0 |
| Where does monthly revenue need to be twelve months from now? | POLISHED: Test answer 51.0 |
| How many people on the team, including the founder? | POLISHED: Test answer 52.0 |
| Rough average deal or order value, if there is one? | POLISHED: Test answer 53.0 |
| Roughly how many qualified leads come in per month today? | POLISHED: Test answer 54.0 |
| Of the leads that reach a conversation, what share close? A rough percentage. | POLISHED: Test answer 55.0 |
| Roughly what does it cost to win one client — ad spend, time, tools, all in? | POLISHED: Test answer 56.0 |
| Rough gross margin percentage on the work you sell? | POLISHED: Test answer 57.0 |
| Hours a week the founder puts into the business, and roughly how many of those go to admin? | POLISHED: Test answer 58.0 |
| The single metric that matters most right now, and where it stands today? | POLISHED: Test answer 59.0 |
| Will you be the primary decision-maker for this engagement? | POLISHED: Test answer 61.0 |
| Is anyone else involved in reviewing, approving, or signing off on scope or proposals? | POLISHED: Test answer 62.0 |
| Who would be our primary point of contact once a project begins? | POLISHED: Test answer 63.0 |
| Is there anything in your internal review process that tends to slow things down? | POLISHED: Test answer 64.0 |
| How do you prefer deliverables presented? | Written document |
| Do you prefer high-level strategic direction, a practical action plan, hands-on implementation, or a mix? | High-level strategic direction |
| Are there any of these in play? | Confidentiality / compliance |
| Any detail on those flags? | POLISHED: Test answer 70.0 |
| Is there anything that could realistically delay or complicate this project? | POLISHED: Test answer 71.0 |
| Is there anything important we haven't covered that we should know before preparing a recommendation? | POLISHED: Test answer 73.0 |
| Is there anything specific you would want reflected in the proposal itself? | POLISHED: Test answer 74.0 |
| Once the proposal is sent, what would the ideal next step look like on your side? | POLISHED: Test answer 75.0 |