You write the brief. The system runs the quarter.
Goals, knowledge, research, content, campaigns, distribution, CRM, ads, analytics and learning on one engine. Nothing publishes and no budget moves without you accepting it.
In development · built in Switzerland, data stored in ZurichWe need 40 qualified meetings from DACH operations leads this quarter. Budget is CHF 60 000. Nothing paid goes live before the pillar article is published.
The loop closes on itself
Most stacks stop at reporting. Here the measurement writes back into the knowledge the next plan starts from, so the quarter after this one begins further along.
Goals
One objective per goal, with the target that was live when the number was measured.
Knowledge
Positioning, audience, tone and product facts, indexed from your own sources.
Research
Scheduled runs that produce findings. A finding without a source is not a finding.
Content
Assets and their variants, each tied to the step that asked for it.
Campaigns
An approved plan in flight, with its budget and its pacing.
Distribution
Channel health, publish windows, and the queue waiting to go out.
CRM
Who came from which campaign, and where they are in the lifecycle.
Ads
Paid spend beside the organic plan, with reallocations proposed, never taken.
Analytics
One reconciled set of numbers, each naming its model and its sync time.
Learning
What was tested, what changed, and which changes became defaults.
A brief, not a form
Write the outcome, the audience and the constraint in plain language. Muse returns nine or so concrete steps, each with a channel, an owner and the inputs it still needs. Edit the plan, remove what you do not want, then approve it. Approving creates the campaign and schedules the work.
If the brief is too thin, Muse asks one question instead of guessing.
The measurement writes back
Every figure names its attribution model and the time it was last reconciled. When an experiment concludes, the winning variant is promoted into knowledge, so the next brief starts from what you already learned rather than from a blank page.
Muse proposes the change. A person accepts it. The log keeps both names.
Priced per workspace, not per seat
Planned prices. MarketThing is in development and not for sale yet. Every plan is to include all ten modules; what changes is how much the engine may run on its own and how many connected sources it reads.
One workspace, two connected sources, and the loop running on approval for everything.
Eight sources, standing research, and automation you scope yourself.
Several workspaces, your own retention rules, and the audit trail your compliance team asks for.