Facebook tracking pixel What is missing | Handbook | Conversion System Skip to main content

Honest list of gaps in CS today

What is missing

A living list of what this business does not yet have. Honesty in public is a brand discipline.

4 min read · Section: Open gaps · Updated 2026-05-29

A branded handbook visual showing operating notes, decisions, and AI system handoffs

This is the list of gaps in Conversion System today. We publish it for the same reason Resend publishes its Known Gaps page. Honesty is a brand discipline, and the list signals which problems we have already accepted as worth our attention.

No live chat on the website

The plan form is the structured intake. We do not run a chat widget because most chat conversations are lower-information than a five-question form. If you want to talk, the plan is the path.

No SOC 2 compliance

Our typical client is a growing business that needs practical AI systems before enterprise procurement paperwork. None of them have required SOC 2 to date. If a future engagement does, we will pursue it. Until then, we are not paying for a certificate that does not change what we ship.

No formal pillar email program yet

The Friday digest ships. The deeper monthly pillar email for tool-completers is sketched but not built. It is queued for Q4 2026.

Public references exist; performance numbers need context

Purple Lotus and The Flower Shop are public Conversion System references. We can talk about the work category now. Performance numbers will publish when each result has a baseline, date range, evidence, and context a buyer can inspect. We do not invent client results.

No call recording on sales conversations

Most calls are short. Recording adds friction (consent, storage, review) without proportional value. If the plan funnel scales past the team's bandwidth, this changes.

No CRM integration beyond Resend properties

The client-side CRM (HubSpot, Salesforce, Pipedrive) is whatever the client uses. We do not maintain integrations with each. The plan data goes into D1 + Resend; the client integrates from there.

No public pricing page

Sprint pricing is per engagement based on the workflow, access needs, review loop, and handoff path. A flat number on the website would be wrong for half of inquiries. The plan is the way the number gets named.

No team beyond the named builders and AI-assisted build stack

The named builders are Angel and Paul. The execution stack uses AI-assisted research, writing, coding, and review tools where they make the work better. We have not hired beyond this. If we do, the hiring philosophy will be published here first.

No annual conference

Resend ran the first Resend Forward in 2026. We are watching to learn from the format. If we run one, it will be small, reference-only, and focused on practical workflows rather than vendor pitches.

This list gets updated

When something on this list ships, it leaves the list and goes into the active handbook. When a new gap surfaces, it gets added here. The page is dated; the date is when we last touched it.

Last updated: 2026-05-29. We re-plan this list quarterly.