Skip to content

THE PLATFORM

we did not buy our operating system, we built it

Most agencies run on a stack of other people's tools and a thread of email attachments. We run on software we wrote. Delivery, approvals, reporting, money, proposals, tasks, and knowledge live in one system, and every client gets their own side of it. You see the work, not a status update about the work.

Built in-house

Not a reskinned project tool. Our own product, shipping every week.

We run on it

Unbound operates its entire book here. Clients get the transparent side of the same system.

Agent-operable

A built-in MCP server lets our AI agents work the platform under the same permissions a person has.

WHAT YOU SEE

the engagement, visible from your side

1.1

a workspace, not an inbox

Each client gets a portal at their own address, not a shared folder. Deliverables, scope, plan, meetings, reports, tasks, and finance in one place, on any device. Access is per person and per section, so a finance contact sees invoices and nothing else, and an operator sees the work and not the money.

1.2

delivery that stays current

Deliverables sync from Google Drive, so what you see is the live file and not a copy that went stale two weeks ago. Every item carries an approval flow: approve it, or request changes with a reason. Six months of work stays searchable instead of collapsing into a flat list.

1.3

accountability that runs both ways

What we owe you is dated, and so is what we need back from you. Pending decisions are first-class blockers, each naming the deliverable it is holding up and how many days it has waited. Every meaningful event lands in an append-only ledger, so there is one neutral record of what happened and when.

1.4

reports written from the actual work

Weekly, biweekly, monthly, quarterly, or per engagement phase. The body is assembled from the real delivered work for that period, with real names and links, and a report files work by when it was performed rather than when it was uploaded. AI drafts the connective narrative, never the facts. Nothing reaches you until a human approves it.

HOW THE COMMERCIAL SIDE RUNS

proposals, documents, and money in the same system

2.1

proposals that provision the client

Branded proposals with separate content and pricing views, shared by link with open, email, or verified access, exportable to PDF. Accept one and the platform drafts the client: the contract, the base deliverables, and the access, all as drafts for a human to review before anything goes live.

2.2

documents you can learn from

Share a deck or a PDF by link and swap the file behind it without the link changing. Choose scrolling or slide-by-slide reading, control downloads, and choose how a viewer gets in. Then see who opened it, what they read, and how long they stayed on each page, with session timing honest enough to ignore a tab left open in the background.

2.3

billing that does not chase

Per-client invoicing with numbers assigned at issue, recurring and phased contracts, and payment by card through Stripe or on-chain in stablecoins across several networks. Automatic reminders, and outstanding balances visible at a glance on both sides.

2.4

one task system, shared

Board and list views, subtasks, dependencies, filters, grouping, and saved views. The team and the client work the same tasks, so a request does not become an email that becomes a missed commitment.

WHAT IT KNOWS

the part that compounds

3.1

a knowledge base that connects

Notes with wikilinks and backlinks, a graph of how the work relates, and knowledge synced from Drive. Resources, collections, and case studies in one library, sorted by language and by type, and shareable to a client or a prospect as a real gallery rather than a wall of text.

3.2

the network, worked properly

Thousands of people met at frontier tech events across AI, Web3, and quantum, held as one deduplicated record per person rather than a spreadsheet. Table, list, and board views, saved slices, ownership, and outreach state in place. This is the network behind our business development and partnership work.

3.3

AI operations, human-gated

Meeting minutes, meeting-to-task extraction, monthly plans, report drafting, profile enrichment, and research all run as background jobs on models we pick per task. Every one of them proposes. A person confirms. Nothing that reaches a client is auto-published, and a field with insufficient evidence is left blank rather than invented.

3.4

built for agents, safely

The platform ships its own MCP server, so an AI agent can operate it the way a team member does, through the same guarded endpoints, scoped to that member's permissions and never further. One hard rule governs it: an agent may prepare anything, but anything irreversible or leaving the company waits for a human to release it.

HOW IT IS SECURED

access is identity-bound, everywhere

Row-level security on every table with no public policy, so the browser never touches the database directly and every read and write goes through the server. Clients and proposal viewers enter by a code sent to an allowed email, and an unknown address is never sent one. Everything a viewer sees is an explicit allowlist of fields, so internal notes, other clients, and analytics cannot leak into a client-facing response.

THE PLATFORM, ANSWERED

what clients ask about it

  • It is included. Every Unbound client gets access to their workspace as part of the engagement. We do not sell it as a separate product.

This is what we mean when we say operators. We do not advise from the outside, we run the work in a system we built, maintain, and use every day, and we hand you the transparent side of it.

see it on your account

Tell us what you are building and where you want to go. We reply within 24 hours.