The hard questions, answered directly.

Decision execution infrastructure is the layer between a decision being made and the work it causes being tracked, owned, and done.

Conductor is that layer. It takes an unstructured directive, decomposes it into typed, owned, dependency-ordered actions, applies guardrails, executes them in the tools the team already runs, and remembers why — so the next decision routes faster.

A wrapper is a single prompt hoping for the best. Conductor is a pipeline: sanitize → triage → synthesize → guardrail → execute → learn. Nothing reaches a tool without passing a policy check, and every approved or rejected card is recorded in per-workspace decision memory.

Honest version: the moat is a thesis being tested, not a proven barrier. The test is whether decision-memory retention compounds across real design-partner usage. That measurement is the point of the next eight weeks.

They draft; Conductor executes. Those tools schedule your tasks, summarize your meetings, or suggest next steps for an individual. Conductor's guardrail pipeline actually creates the Linear ticket, sends the Slack message, and closes the loop — across the team's tools, with an audit trail of who decided what and what happened.

The buyer is different too. Those are individual-seat sales. Conductor sells to an operations or engineering function with coordination overhead — a buyer with real budget and a seat-expansion path.

Zapier executes deterministic rules on structured triggers: when X happens in this app, do Y in that one. Conductor interprets unstructured intent — a sentence a human wrote — applies judgment-shaped guardrails, and decomposes it into typed, dependency-ordered, owned actions.

Different job-to-be-done. Zapier automates the predictable. Conductor handles the judgment calls, which is where coordination budget actually goes.

Nothing, inside their own tools — they will build governed AI features there, and that threat is real. It should be named, not dismissed.

Conductor's differentiation is being tool-agnostic and protocol-native (MCP) across a stack no single vendor owns end-to-end. The counter is speed and the decision-memory data asset — not a permanent technical barrier, and the pitch doesn't pretend otherwise.

It's a feature if the wedge stays “founder productivity.” As decision execution infrastructure sold to ops and engineering functions, there is an existing budget line (workflow and automation spend), organic seat-by-seat expansion, and a per-workspace data moat that compounds with usage.

Said plainly: this is unproven until design-partner usage data exists. The raise exists to produce that proof.

Because founders are a weak buyer for this product. Small budgets, no seat expansion — a solo founder never buys a second seat — and the most crowded category in AI tooling, where Motion, Lindy, Xembly, and alfred_ all chase the same person.

The pain Conductor solves best — “who owns this, and did it actually happen” — is felt hardest by operations and engineering leads at 20–150 person companies running Linear and Slack. That buyer already budgets for coordination tooling, and expands naturally as teammates start receiving Delegate cards and submitting their own directives.

Proven: the pipeline executes end-to-end today in Linear, Slack, Notion, and Gmail. Decision memory is live (pgvector + HNSW, sub-50ms retrieval). Average model cost is $0.0004 per directive.

Modeled: the 15+ hours per week teams lose to decision translation is a modeled figure, not a measured one. It will be replaced with measured data from design partners.

Not yet proven: product-market fit. Conductor hasn't been in front of design partners matching the new ICP yet. Recruiting five to eight of them is the highest-priority item in the company.

Two things changed. First, structured output from frontier models crossed a usability threshold in roughly the last twelve months — unstructured human intent can now reliably become typed, executable structure. That wasn't true when the current category leaders were built.

Second, as AI agents proliferate, organizations will need a governed execution plane between intent and action. Conductor is MCP-native from day one, built to be that plane. Stated as a bet, not a claim, until there's usage evidence behind it.

There's no pricing page yet, deliberately. The direction is a base workspace platform fee plus per-active-seat delegation pricing, so price tracks the value driver: the more people route decisions through Conductor, the more valuable it is.

Flat per-seat pricing at $49–149 undersells the expansion mechanic and caps revenue below what an operations-infrastructure tool should command. Pricing gets finalized against design-partner usage data, not before.

The raise is $50,000 — a small pre-seed round, and the size is deliberate. It funds Phase 1: eight weeks shipping the core loop into five to eight design partners' real workflows, instrumenting decision-memory usage and retention, and converting the result into a one-page proof doc with measured retention, time-to-first-value, and seat-expansion signal.

A seed round sized to evidence comes after the proof exists. Pairing a small ask with big-round language would be a credibility gap, and this raise is structured to avoid it.

Four, named plainly:

• Solo-founder execution capacity. One engineering hire is the first use of funds.
• Scope versus resources. Seven expansion modules sit on a 40-week roadmap — sequenced so the wedge works without them.
• Unproven product-market fit. No design partners against the new ICP yet.
• Incumbent platforms. Microsoft and Atlassian will build adjacent features inside their own tools.

The next 90 days are built to attack the first three directly.