MetAiBlock Prepared for Elena · August 2026
Maison HQ · Validation & Pre-Development Retainer

Prove it before you build it.

You have the idea, the decks, and the flows. What is missing is the evidence. This puts real market data underneath Maison HQ, so the build starts from proof instead of instinct.

12Weeks to build-ready
0Lines of code first
3Tracks in parallel
1Milestone: MVP build start
The objective

Reach a build-ready Maison HQ with a proven customer, a justified feature set, and users already waiting.

The work

Consulting plus pre-development coordination on a weekly cadence, running until the MVP build starts.

The outcome

A developer-ready spec, quantitative ICP proof, a pre-launch list, and an investor evidence pack.

The investment

A flat monthly retainer for 12 weeks. No build cost until the spec is signed off.

1

What we heard

From our conversation on August 19. Your words, not our summary.

“A home intelligence profile that anticipates the needs of a home.”

Elena · on the Maison HQ thesis

“Almost like a Carfax, but a house fax.”

Elena · on the 1893 Chicago house

“We’re looking through Facebook HOA groups and on Thumbtack.”

Elena · on how homeowners find help today

“I know this is going to take a strong go to market push.”

Elena

The one gap you named yourself

On whether the customer is proven: “I wouldn’t say that I have proven it.” You have done informal reads on social. None of it is documented in a form an investor or a partner can trust. That gap is the whole reason this proposal exists.

2

The two ideas, and the call

You brought two. Both are real. Only one deserves your energy this quarter.

Focus here

Maison HQ

A digital house manager for homeowners who cannot justify a human one.

  • Predictive maintenance across the home and its systems
  • Provider matching that learns how you buy
  • Service history and contracts in one place
  • Connects into existing marketplaces, does not replace them

Ready: investor deck, developer deck, homeowner flow (20 screens), provider flow, admin panel, phased rollout.

Missing: proof, a user list, and a spec a developer can price.

Park it, briefly

Bake Sale

A marketplace for the cottage food industry, with state rules built into the data.

  • Genuinely underserved, and you are close to an MVP
  • State-by-state compliance already modeled
  • You can carry it yourself, which is exactly why it waits

Bake Sale is the one you can finish alone on a quiet weekend. Maison HQ is the one that needs a team, and the one you told us you cannot do by yourself. Energy split across both slows the harder one down.

Two good ideas competing for the same hours is the most common reason neither ships.

The one objective

Arrive at the first line of code already knowing who buys, what they pay for, and which features earn their place.

Everything in the next 12 weeks serves that one sentence. Nothing else gets built, bought, or branded until it does.

3

Where the risk actually sits

Building Maison HQ is not the hard part. Reaching the market is. Most founders discover that in the wrong order.

THE COMMON PATH Idea Build everything Launch Who wants this? Rebuildor run out of runway THE PATH WE RECOMMEND Idea Validatesurvey + campaign Specdata picks features Build the MVPscoped and priced Launchto a waiting list The difference is not speed. It is what you know when you start spending. The top path pays for features nobody asked for, then pays again to remove them. The bottom path spends once, on the things the market already told you it wants.
4

One campaign, two assets

The validation work is not a cost you absorb to get comfortable. It produces two things you keep.

Survey + campaign to your ICP, before code Asset 1 · Proof Ranked pains, willingness to pay, a customer profile that holds up Asset 2 · A user list Named homeowners who raised a hand before you launched The build gets cheaper You only pay to build what earned its place in the data The raise gets easier You answer “have you proven this?” with numbers, not conviction

The same work that de-risks the build is the work that funds it. That is why it goes first.

5

What the retainer covers

Two jobs in one engagement: the thinking, and the coordination that turns thinking into a buildable spec.

Strategic consulting

  • Weekly working session, standing time
  • Sequencing calls: what comes before what
  • Founder decisions pressure-tested before you commit
  • Direct access between sessions for live questions

Pre-development coordination

  • Feature set ranked against real demand data
  • Agent architecture mapped, not guessed
  • A spec a developer can price and execute
  • Build partner evaluation and handoff

A dedicated cadence

  • Weekly session, same slot, every week
  • A written readout after each one
  • Running action list owned on both sides
  • Runs until the MVP build starts, then stops

What this is not. This is not a build contract and it is not open-ended advisory. It has one finish line: the moment your MVP build starts with a signed-off spec. At that point this engagement has done its job.

6

The path from retainer to build start

Twelve weeks, four stages, one milestone. Every stage produces something the next one needs.

1 Weeks 1–2 Focus Lock the venture, define the ICP, design the survey 2 Weeks 3–6 Signal Campaign live, list growing, weekly data readouts 3 Weeks 7–9 Decide Rank features on evidence, cut the rest, set pricing 4 Weeks 10–12 Build-ready Write the spec, map the agents, select the builder Milestone MVP build starts You said 90 days to get started. This lands you there with the proof already in hand.
Stage 1 output

A locked scope and a live survey

One venture chosen. ICP written down in testable terms. Survey and campaign built and pointed at real homeowners. Your capture system stood up before the first response lands.

Stage 2 output

Data arriving every week

Responses collecting, list growing, social presence publishing. You see a readout weekly, so the picture forms in front of you instead of arriving as a surprise at the end.

Stage 3 output

A feature set you can defend

Every candidate feature ranked against demand. The MVP line drawn on evidence. Pricing signal captured. The cuts are the valuable part.

Stage 4 output

A spec a developer can price

Functional spec, agent architecture, data model, and acceptance criteria. Enough that any competent build team can quote it and you can verify what comes back.

7

Three tracks, running together

You told us the build and the raise would move in parallel. They can, as long as the audience is being built at the same time.

Track 1 · Validation Survey design → campaign live → responses ranked → ICP proven → features cut to the MVP line Owns the answer to: what do we build, and for whom Track 2 · Capital raise support Evidence pack → demand charts → AI architecture story → traction slide backed by named users Owns the answer to: have you proven this, and why is AI core to it Track 3 · Audience and presence Content without a logo → social aggregation → list capture → weekly reporting on what resonates Owns the answer to: who is already waiting on launch day MVP build starts

One engagement drives all three. They share the same weekly session, the same data, and the same finish line.

8

What survives the MVP

You estimated around 30 agents at full build. The MVP is not a smaller version of that. It is the smallest thing the data says people will pay for.

The full vision Maintenance, providers, contracts, documents, lifestyle, events Filtered by demand Ranked by what homeowners said they would pay for The MVP Small, defensible, fundable

Why the cuts matter more than the build

  • Every feature you cut is development budget you keep
  • Every feature you keep arrives with a reason attached
  • Investors test the cuts. A founder who can explain what they chose not to build reads as disciplined
  • Developers price scope. A tight scope quotes lower and ships sooner

Your instinct on the call was right: the later versions carry the lifestyle layer. This confirms which parts of that belong in version one, and gives you the evidence to hold the line when the scope wants to grow.

9

The system you keep

This engagement leaves infrastructure behind, not a slide deck. All of it keeps working after the build starts.

A customer record from day one

Every respondent captured, tagged, and tracked from the first campaign. On launch day you are emailing a list, not buying an audience.

Social aggregation

Publishing and listening across the channels your buyer actually uses, pulled into one place. Content can run before the brand exists.

Weekly reporting

What was asked, what came back, what it means, and what changes because of it. The same report doubles as investor evidence.

Build the audience while the brand is still undecided

You do not need a logo, colors, or a name locked to start earning attention. Content that speaks to a homeowner problem builds trust now, so when Maison HQ does launch, the market recognizes it instead of meeting it.

10

What we need from you

Short list. Most of it you already have.

To start

  • The investor deck and the developer deck
  • The homeowner flow, provider flow, and admin panel screens
  • Your phased rollout notes
  • A standing weekly slot that you protect

Along the way

  • Decisions when we bring them to you, inside a week
  • Access to your network for the first survey push
  • Your read on which cuts hurt, so we test the right ones
  • Honesty about capacity, so the plan matches your real hours
11

Investment

One retainer, one cadence, one finish line. No development cost until the spec is signed off.

The engagement

Validation & Pre-Development Retainer

Consulting plus pre-development coordination, on a weekly cadence, for 12 weeks or until the MVP build starts.

  • Weekly working session, standing slot
  • Written readout after every session
  • Between-session access for live decisions
  • All three tracks driven from one engagement
  • Ends at the milestone, not on an open clock
$__,___

per month · 12 weeks

Final figure confirmed with Charles
before this page is shared.

What is included

Everything in sections 5 through 9: the sessions, the survey and campaign design, the capture and reporting setup, the feature ranking, the spec, and the build-partner handoff.

What is separate

The MVP build itself, paid media spend, and any third-party tooling. All of it is scoped and priced during stage 4, so you approve it with the data in front of you.

12

What comes after

Not part of this proposal. Worth seeing, so the road is visible from here.

The MVP build

Scoped and priced from the spec, with the option to build through our team or hand the spec to yours.

Launch to the list

The audience built in track 3 becomes your first cohort, with the campaign already warm.

The agent layer

The wider agent set you described, added in versions after the market has confirmed the core.

13

Fair questions

Why not just build it? We are losing time.

You would not be losing time, you would be spending it in the most expensive place. Code is the costliest way to discover you built the wrong feature. Twelve weeks of evidence typically removes more from the build than it adds to the calendar, and it arrives with a user list attached.

We already know our customer. Is validation really necessary?

You know them well, and your demographic work is genuinely detailed. What is missing is not the insight, it is the documentation. On our call you said it plainly: you would not say it has been proven. An investor or a partner cannot act on a founder’s conviction. They can act on a survey.

Can we run Bake Sale at the same time?

You can, and it will cost you Maison HQ’s momentum. Bake Sale is small enough to carry alone, which makes it the safer one to pause. The recommendation is to bring Maison HQ to a build start first, then let it create the capacity that makes running both realistic.

What if the data says the idea is wrong?

Then it saved you a build. That outcome is rare in this shape, because the gap you identified is real, and the evidence usually reshapes the feature set rather than the premise. Either way you learn it for the price of a survey instead of a development cycle.

14

Next steps

Three things move this forward.

1
Confirm you have read thisElena

A short reply is enough. It tells us the page landed and nothing is stuck in a spam folder.

2
Book a working sessionElena

Thirty minutes to walk the plan, challenge it, and adjust the parts that do not fit how you work.

3
Send your reaction, including the parts you disagree withElena

Especially where the sequencing feels wrong or the scope feels heavy. The plan is better after you push on it.

Book the working session Send your thoughts