The moat under the engine

One Blueprint. Every product gets sharper.

The Blueprint is the shared context layer under the Cafiyn Go-To-Market Engine. Lens writes the market model, FlyWheel runs against it and writes the outcomes back, so each campaign sharpens the next assessment. Included in every plan.

See the plansSee both products
What it holds

What the Blueprint holds, one truth.

The Blueprint is not a database of everything. It is six categories of context every founder needs, curated by the product that knows each one best.

Buyer intelligence

ICP definitions, buying committees, personas, and the exact wedge that separates you from the top three alternatives.

Market opportunity

Demand signals, category maturity, competitive matrix, and pricing anchors specific to your segment.

Positioning + messaging

What you say and to whom, versioned. Outbound reads the same source as the landing page, so the two cannot drift apart.

Objection library

What buyers push back on, in their words. Lens predicts them; FlyWheel discovers the real ones and writes them back.

Campaign outcomes

Which segments replied, which channels worked, which accounts closed. The evidence that revises the market model.

Decision history

What you targeted before, what happened, and why you changed. The part no exported CSV ever carries with it.

How it grows

Two products in. One loop that closes.

Each product writes what it learns and reads what the other discovered. The order matters: Lens seeds it, FlyWheel tests it, and the result comes back.

Cafiyn Lens

Writes: ICPs, buying committees, competitor teardowns, positioning wedges, Market Viability Score, demand signals.

Reads: Which segments actually replied, which messaging won, and which accounts closed. Every campaign outcome revises the next assessment.

Cafiyn FlyWheel

Writes: Wheels processed, prospect responses, objections raised, meeting outcomes, closed accounts, channel performance.

Reads: ICP, buying committee, positioning, and objection library, so outbound goes to the right people already sounding like you.

Why it matters

The moat is not the products. It is what they share.

A stitched SaaS stack can imitate any single Cafiyn product. It cannot imitate the shared Blueprint that makes each product sharper than its standalone equivalent.

A loop, not a handoff

Any tool can import a list. What a stitched stack cannot do is send the result back: your outbound results changing what your market research concludes next month, automatically, without anyone re-keying anything.

It compounds with use

The first campaign runs on what Lens inferred. The fourth runs on what actually happened three times. Nothing about that improvement requires you to do extra work, which is the whole point.

Private by default

Your Blueprint is scoped to your business only. What you ask any Cafiyn product is never training material for anyone else. Privacy, security, and transparency come first.

Portable, and yours

A single Blueprint per business. Change tier, add a product, drop one, export it entirely: the context follows you and there is nothing to re-onboard.

Pricing

The Blueprint is included in every plan.

No add-on fee. No per-seat surcharge. The Blueprint grows with whichever products you use and moves with you as you upgrade.

Ignition

$29/mo
  • FlyWheel (100 Wheels)
  • The Blueprint
  • Lens optional from $14.99
Start Ignition

Trajectory

$49/mo
  • FlyWheel (200 Wheels)
  • The Blueprint
  • Lens optional from $14.99
Start Trajectory
Most popular

Orbit

$99/mo
  • FlyWheel (450 Wheels)
  • The Blueprint
  • Lens optional from $14.99
Start Orbit

Command

$199/mo
  • FlyWheel (1,000 Wheels)
  • The Blueprint
  • Lens optional from $14.99
Start Command

Enterprise

Custom
  • Custom Wheel volume
  • Cafiyn Lens bundled (25/mo)
  • Founder-led onboarding + SLAs
Talk to us

All prices in USD. Billed monthly, cancel anytime. Full plan comparison at /pricing.

Blueprint questions

Honest answers about the layer under everything.

Is the Blueprint a product I buy separately?

No. The Blueprint is the shared context layer under every Cafiyn product. It is included in every plan and grows every time either product runs. There is no add-on price for it.

What actually lives in the Blueprint?

Buyer intelligence, market opportunity, positioning and messaging, the objection library, campaign outcomes, and decision history. Every category is scoped to your business only, and each one is written by one product and read by the other.

How does the Blueprint compound?

Lens writes the market model: who to target, what they care about, what they will object to. FlyWheel runs against it and writes back what actually happened: who replied, which segment converted, which objection was real. That evidence revises the model, so the next assessment and the next campaign both start from what you learned rather than from what you assumed.

Is my Blueprint used to train Cafiyn or anyone else?

No. Your Blueprint is scoped to your business only. What you ask any Cafiyn product is not training material for anyone else. Privacy, security, and transparency come first.

What happens to the Blueprint if I cancel?

You can export it at any time in a portable format. If you cancel, you keep the export. We keep no operational copy beyond the retention window in our privacy policy.

Can I use the Blueprint outside Cafiyn products?

Read-only access via an export API is on the roadmap for Enterprise customers. The whole point of the Blueprint is that it stays live inside the engine; static exports are for portability and audit, not day-to-day use elsewhere.

Where does the Blueprint live physically?

Cafiyn Cloud today. Enterprise customers can opt into regional data-residency (EU, US, IN) as those regions come online. Enterprise-grade encryption at rest and in transit; least-privilege access; audit trails.

How is the Blueprint different from a CRM?

A CRM stores records you enter and enrich by hand. The Blueprint is written automatically by the products as they work: Lens writes the market model, FlyWheel writes campaign outcomes, and each revises the other. It holds why a decision was made, not just who you contacted, and it feeds back into the next run rather than sitting as a static database.

Do I need both Lens and FlyWheel for the Blueprint to be useful?

One product still writes to it and reads from it, so a single product benefits. The compounding effect, where campaign outcomes sharpen the next market assessment, only happens with both. That closed loop is the reason the two modules are built to run together.

Can a competitor copy the Blueprint?

They can copy either product. They cannot copy the loop between them running against your specific market for months. A stitched stack of separate tools can imitate any single feature, but the outcomes never feed back to sharpen the model, because the tools do not talk to each other. The Blueprint is the moat precisely because it is yours and it compounds.

Ready when you are

Start the Blueprint on your first Wheel.

Every plan starts writing to your Blueprint from day one. The more you use, the sharper every product gets.

Start with FlyWheelSee all plans