The workspace your team's agents work in.
Everything your team knows, and the tools to work on it, kept as files that every agent reads. It runs on the AI subscriptions the team already has.
The files
Client briefs, proposals, decisions, brand rules, decks, sheets and data. Every change is versioned, and every machine has the same copy.
The tools and interfaces
Views built for the firm's own work: documents, sheets, decks, contact lists and progress widgets.
The team's own agents
Claude or ChatGPT on each person's own subscription, working locally on the files, in the Syns app (bb underneath). Nobody needs a terminal.
Setup
- Sign in with Google
- Describe the company
- Import from Drive
- Accept the proposed structure
- Connect the agent
Work
- Ask for the work in plain words
- The agent reads the client's briefing first
- The deliverable builds in the client's folder
- Widgets and data stay in one place
Collaborate
- Teammates join, each with their own agent
- Comment on a file and tag an agent
- The agent makes the change
- Everyone's agent reads the same brief
Forever, for one person: one synchronised workspace, with insight widgets.
Team plan, from the second member ($10 billed yearly). The AI is paid to its vendor, not to us.
Not: branches or pull requests · two people typing into the same text · reselling the model · storing prompts · hosting source code. product.md
Client-service teams of 2 to 10 where several people work on the same client, each with their own AI.
Who
Boutique agencies, studios and consultancies that already pay for AI and use it on client work. The owner or a partner buys. Next: founder-led product teams. A way in: solo fractionals. Secondary: developer teams.
Not for
People doing one assignment at a time or using AI only occasionally, large firms with procurement, work that may not be hosted, source-code hosting, prompt marketplaces.
The pain: what one person told their AI about the client never reaches a colleague's AI.
"The current method of sharing these files via Slack is ineffective because team members do not consistently read them."Arthur Moreau, founder, from the notes of his first call. The cost he named: his colleague stops using her own judgement and copies his examples.
- The hook everyone feels: every session starts from zero, and people spend 5 to 10 minutes re-explaining the client each session, for each client.
- Output that ignores the brand or the client's template.
- One method copied into every client project, with the copies drifting apart: "Four Projects meant four copies. Fix a phrase in one and the other three were quietly wrong until I remembered."
- Months in: the brief goes stale after the client changes something, and the next piece of work comes back confident and wrong.
How to qualify them: they describe the brief not reaching a colleague before we mention it. audience.md
Why a team picks Syns, and why it is hard to copy.
Their agents, their subscription
The team pays its AI vendor for the agents, not us, and that holds even for a team on a single vendor. Any vendor's agent works in the workspace. An AI vendor gains nothing by making a rival's model better.
A workspace made for the company's task
Custom interfaces and custom tools for exactly the work the firm does, with all its tools and data in one place for the agent. It is where the work gets done, not just a memory the agent reads from.
Local files
For the agent, the workspace is files on its own filesystem: no tool calls, no round trips, and always in view. That is more efficient than anything reached through MCP or a CLI.
It follows the work across companies
Client material sits in the client's accounts and the method in the firm's own. Platforms built around one company account can't follow the work across that line.
It knows what every agent read
It records which agent read which version of which line before it wrote. That record is what lets Syns catch a brief drifting from what was agreed, and nobody else holds it.
Every workspace teaches the next
Structures, tools and interfaces that work for one kind of engagement become the starting point for the next client.
positioning.md § The moat
A beachhead that can carry $1M a year in the EU, but not $10M.
- A paying team brings $24 to $35 a month. The risk is teams of one or two people.
- Holding $1M a year at median churn takes about 76 to 112 new paying teams a month. That growth has to come from teams inviting each other, which is why pricing starts at the second person.
- Beyond the beachhead: IT consultancies (~146,000 EU firms, already working in agents), firms of 10 to 49, and developer teams.
Official CBS, Eurostat and Census data, read 24 Sep 2026. Every figure is an upper limit. pricing-research
Every investor has asked for the same thing: teams using it.
So the plan is to show that client-service teams use Syns every week and start paying, then raise before the runway ends.
- 9 Oct 2026Problem conversations with client-service team ownersactive
- 31 Oct 2026The Syns app works for a client-service teamactive
- 15 Nov 2026The demo video is out, and the applications are sentplanned
- 15 Dec 2026Three design partners, client-service teams using it every weekplanned
- 1 Jan 2027A funding commitment on recordplanned
- 31 Jan 2027Teams active, and the first team payingplanned