Back to portfolioAgent infrastructureProject 04

Daisy+

Three purpose-built interfaces — operations, technology, and executive orchestration — running on the same first-party data, connected by MCP.

Daisy+Selected work

Domain: Agent infrastructure
Stack: MCP · multi-interface · first-party data
Surfaces: Three

Visit the live experience

ROI

Project impact

What the work changes.

Constraint

Operations, engineering, and leadership needed different controls without fragmenting data, permissions, or agent activity.

Intervention

Three role-specific interfaces were connected to the same first-party data and orchestration layer.

Business effect

Each team gets the view it needs while the business retains one governed source of truth.

Context

The brief

Start with the tension, not the treatment.

Agents that persist across sessions and act across systems need somewhere to run safely. Operations, engineering, and leadership each need a different view of the same activity, and bolting three tools together leaves the data — and the permissions — fragmented.

System

The deliverables

What we delivered, layer by layer.

01
daisyplus.io for operations: CRM, sales, inventory, and e-commerce.
02
daisyplus.net for technology: an AI workflow builder, LLM routing, and permissions.
03
daisy.plus for executive orchestration: agent visibility, strategic control, and human review.
04
All three run on the same first-party data, connected by MCP, so a role-scoped view is a view rather than a copy.
05
Agents run in production with defined roles, permissions, and human oversight — the infrastructure for systems that take actions over time, not chatbots that answer single prompts.

Recorded evidence

Only documented project facts appear here.