The aggregate demand question the lane should keep most visible.
Project audience
Audience health, segment mix, and governed demand watch.
Safe project-level audience view for lead quality, segment mix, governed watch controls, and demand signals without exposing contact details.
Live publishingRefine migration activeCadence: Monthly issue cycleRead-only previewUpdated Apr 12, 2026, 3:47 AM UTC9 total leadsRevenue-ready demand
Refine runtime
The audience lane now owns a safe project mutation path instead of staying purely observational.
Aggregate demand posture still lands on first paint from the server baseline, but operator sessions can now save the current audience focus, watch window, and project note without exposing contact-level lead detail.
Server baseline readyRevenue-ready demand7-day demand watch9 total leadsRead-only previewSynced Apr 12, 2026, 3:47 AM UTC
Hydrating the audience resource on top of the server baseline so demand posture stays readable.
The time horizon currently guiding the audience review loop.
Near-term commercial demand versus the most recent inbound volume.
Safe audience controls now belong to the project workbench instead of operator chat.
All lead submissions tied to the current project acquisition surface.
Qualified demand with the strongest near-term commercial signal.
Demand that still needs timely operator attention.
system-default
Demand watch
The project can now keep aggregate demand posture explicit inside the workbench.
- Current watch: Revenue-ready demand on a 7-day demand watch.
- Operator note: Keep revenue-ready demand visible while follow-up pressure and recovery-state buyers stay readable from the aggregate lane.
- Hot demand: 3 hot leads and 2 attributed leads remain visible from the aggregate layer.
- Scope rule: only authenticated operator sessions can save audience watch controls, and the lane still avoids contact-level lead records.
Landing paths
Which surfaces are pulling demand into the project.
| Landing path | Leads | Share |
|---|---|---|
| / | 3 | 33% |
| /founding | 2 | 22% |
| /index | 2 | 22% |
| /briefs | 1 | 11% |
| /briefs/sample-issue | 1 | 11% |
Top sources
Traffic and lead quality should be visible together.
| Source | Views | Leads | Lead rate |
|---|---|---|---|
| / home | 137 | 3 | 0.0% |
| /index index | 30 | 2 | 0.1% |
| /founding founding | 14 | 2 | 0.1% |
| /briefs dispatch-overview | 11 | 1 | 0.1% |
| /briefs/sample-issue dispatch-sample | 10 | 1 | 0.1% |
| /pricing pricing | 13 | 0 | 0.0% |
| /blog blog-index | 12 | 0 | 0.0% |
| /blog/useeffect-vs-useeffectevent-react-19 blog-article | 9 | 0 | 0.0% |
Segment mix
Offer and intent distribution define who this project is attracting.
- FLUENTREACT Dispatch: 2 leads, 22% of the mix.
- FLUENTREACT Index: 2 leads, 22% of the mix.
- Founding Access: 5 leads, 56% of the mix.
- I want founding access first: 9 leads, 100% of intent demand.
- Solo builder: 3 leads from this role segment.
- Job seeker: 6 leads from this role segment.
Follow-up groups
The audience lane should still suggest where the operator should look next.
- Homepage converts: 3 leads, 0 due, 3 hot. Route them toward the strongest current proof page instead of trying to sell every product shape at once.
- Index page prospects: 2 leads, 0 due, 2 hot. Ask which fluency test or repair drill would make the Index worth paying for before you widen the question bank.
- Founding page prospects: 2 leads, 0 due, 2 hot. Lead with founder timing, bundled value, and what would make the pilot worth paying for this month.
- Dispatch overview readers: 1 leads, 0 due, 1 hot. Position Dispatch as the lowest-maintenance paid offer and ask what monthly verdicts they would actually pay for.
- Sample issue readers: 1 leads, 0 due, 1 hot. Use the sample issue as proof, then ask whether the monthly memo alone or the founder bundle feels stronger.
Recommendations
Aggregate demand becomes useful only when it turns into next moves.
- Blog traffic is still leaking intent: Blog articles have 106 tracked views but only 0 lead-attributed first touches so far. Keep tightening inline founder language on the highest-view posts and move more authority articles toward the strongest paid path.
- Pricing reads are not turning into leads: Pricing has 13 views without a recorded direct lead source yet. Shorten the jump from price to founder form and reduce any copy that feels like policy instead of buying guidance.
- Founding Access is proving broader willingness to pay: Founding Access has 5 leads against 2 for Dispatch. When Paddle approval lands, wire checkout on the founder path first and keep Dispatch as acquisition proof instead of the first standalone checkout target.