For expert-led service companies

Your company, thinking as one.

We build the AI-native operating system for your company.

Your knowledge, decisions and repeatable work become company memory, operating agents and one command centre.

Register interest
An architectural plan becoming an inhabited, connected company campus.
Scattered knowledge
One company system

01 — The problem

Your company keeps starting again.

The work gets done. But too much of the company disappears into people, inboxes, meetings and disconnected tools.

01

Knowledge stays trapped.

The best judgement lives in a few experienced people. The company cannot use it unless they are in the room.

02

Work resets each time.

Every brief, proposal and project begins by rebuilding context the company has already paid to create.

03

AI sits at the edge.

Your team uses AI tools, but those tools cannot see the whole company or act within clear rules.

02 — What we build

We build your Nexus.

A Nexus is the operating architecture that makes the company searchable, usable and able to improve its own work.

01 / 04

Company memory

Your knowledge, decisions, standards and past work in one living source of truth.

02 / 04

Decision system

Clear rules, context and advisers that help leaders prepare, decide and review.

03 / 04

Operating agents

Purpose-built agents for repeatable work, with defined limits and human approval.

04 / 04

Command centre

One calm interface for asking questions, directing work and seeing what is happening.

03 — Built for

Companies whose value lives in people.

Agencies, consultancies and specialist firms share the same problem: their most valuable knowledge lives in people and disappears between projects.

Make every project build the next.

Keep the company's judgement, client context and delivery method alive across every piece of work.

  • Start new work with the context the company already has.
  • Turn senior judgement into reusable standards.
  • Build agents for research, proposals, delivery and handover.
  • Make each finished project improve the next one.

04 — The engagement

Build beside the company. Transfer only what works.

We do not replace the current business overnight. We find the strongest starting point, build the new system beside it and move work only after it earns trust.

01

Diagnose

Find where the company loses time, knowledge and profit.

Company map
02

Design

Define the architecture, rules, agents and first high-value workflows.

Nexus design
03

Build

Install the memory, agents and command surface around real work.

Working system
04

Transfer

Train the team, document the system and leave the company able to run it.

Client ownership

05 — Working evidence

Built from a system we use ourselves.

Dreamwith grows from the operating architecture behind melis.ai and Sean's own work.

This is how the company remembers, decides and acts. Written rules give agents context. Clear authority keeps people in control. Every finished job adds to the company’s memory.

Nexus anatomy / melis.aiillustrative operating extract / v0.3

01 / Company memory

melis.ai/ ├── COMPANY.md ├── MISSION.md ├── STRATEGY.md ├── CONSTITUTION.md ├── NOW.md ├── 00-INBOX/ │ ├── briefs/ │ └── unclassified/ ├── 01-LEADERSHIP/ │ ├── decisions/ │ ├── meeting-rhythm/ │ └── advisers/ ├── 02-COMMERCIAL/ │ ├── offers/ │ ├── pipeline/ │ ├── proposals/ │ └── customers/ ├── 03-DELIVERY/ │ ├── playbooks/ │ ├── active-work/ │ ├── handovers/ │ └── quality-reviews/ ├── 04-MARKETING/ │ ├── campaigns/ │ ├── content/ │ └── distribution/ ├── 05-FINANCE/ │ ├── forecasts/ │ ├── invoices/ │ └── margins/ ├── 06-PEOPLE/ │ ├── roles/ │ ├── capacity/ │ └── hiring/ ├── 07-LEGAL/ │ ├── contracts/ │ ├── approvals/ │ └── data-controls/ ├── 08-KNOWLEDGE/ │ ├── company-memory/ │ ├── methods/ │ ├── evidence/ │ └── pattern-library/ ├── 09-AGENTS/ │ ├── coordinators/ │ ├── specialists/ │ └── schedules/ ├── 10-WORKFLOWS/ │ ├── triggers/ │ ├── approvals/ │ └── handoffs/ ├── 11-CONNECTORS/ │ ├── mail/ │ ├── calendar/ │ └── client-systems/ ├── 90-SYSTEM/ │ ├── audit-log/ │ ├── permissions/ │ └── [REDACTED MODULE] └── COMMAND-CENTRE/

02 / Agent architecture

People set direction. Agents organise the work.

Human authority sits above the system. Each level beneath it has a written job, bounded context, permitted tools and a clear point where work must return to a person.

L0
Human
Leadership team and staffMission · priorities · approvals · final authority
Human authority
L1
Exec
CodexChief of Staff · context · priorities · delegation
ClaudeHead of Design · direction · systems · craft review
L2
Heads
Head of CommercialMarket to signed work
Head of AccountsClient context and growth
Head of DeliveryBrief to handover
L3
Agents
Market scoutOffer strategistPricing analystProposal builder
Client researcherRelationship analystContext keeperRenewal planner
Brief interpreterProject plannerQuality reviewerHandover writer
L4
Jobs
Morning priorities
Daily · 07:00
Pipeline scan
Weekdays · 08:00
Project pulse
Daily · 17:00
Content reuse scan
Weekly · Monday
Finance check
Weekly · Friday
Memory return
After completed work
Approval gates
Stop before consequence
Audit trail
Record what changed
Escalation path
Return uncertainty upward

Memory gives the system context. Authority sets its limits. Workflows turn decisions into repeatable action.Selected architecture only · private modules redacted

06 — Why Horizon 3

Most AI projects improve the old company. We design the next one.

Training people to use ChatGPT is useful. It is not the same as designing a company that can remember, reason and act through one connected system.

H1 — Improve

The old company, faster.

AI helps people inside the current process. The tools and roles remain largely the same.

An inherited factory where people use small AI tools around the existing process.

H2 — Redesign

The work itself changes.

Agents join the workflow. Steps collapse. People move from completing every task to directing the system.

The inherited factory reorganised around automated workflows and a smaller human control team.

H3 — Rebuild

The company itself changes.

A separate successor is designed around shared memory, agents and new economics from the beginning.

A separate circular AI-native facility with a central human command room and modular work cells.
A nature-filled future company campus moving from graphite drawing into an inhabited building.

Founding companies

Be one of the first companies we build with.

We are preparing a small number of founding engagements for expert-led service companies. Tell us where your company loses time, knowledge or momentum. We will contact the strongest fits when delivery opens.

No commitment. This is an enquiry, not a marketing subscription. We will use your details only to assess and respond to your interest. Privacy.

Read the founder manifesto