Case study: how the loop works
One product, four tools, each with one job. marketinque plans, Next Big researches, ppl.studio makes the content and Control Center keeps score. This page follows one launch plan step from a button press to a finished result, shows what was run for real on 12 November 2026, and lists what can never happen without a person.
Four tools, four jobs
They do not share a database or a login. They share a protocol: a plan step, a work order, a result.
Live
marketinque · Plans and decides
Holds the launch plan, the approvals and the log. It is the only tool that can say yes to something leaving the building, and the only one that tracks leads.
Coming soon
Next Big · Researches
Finds competitors, keywords and trending topics for a project and sends back a short, checked report.
Coming soon
ppl.studio · Makes the content
Turns a product page into a launch film in three cuts (vertical, wide, square) and plans what to post when.
Coming soon
Control Center · Keeps score
One table of every project: visits, search, leads, mail, posts and the state of every work order, with an alert when one gets stuck.
The loop, in four moves
Move 01
A plan step says who can do it
Every step in the launch plan is either yours or delegable. A delegable step names the kind of worker it needs: research, or content. Nothing is sent yet.
Move 02
You press the button; it becomes a work order
A work order carries the product name, the address of its site and what is wanted, and nothing else. No logins, no keys, no budget. It waits in a queue in marketinque.
Move 03
The worker pulls it
The worker asks marketinque for orders of its own kind, claims one, and does the job on its own computer. Marketinque never calls into the worker, so there is nothing to open up or attack. A claim lasts a set time; if the worker disappears, the order goes back in the queue, up to three attempts.
Move 04
The result comes back as evidence
A summary, links to what was made, what it cost, and the steps only a person can do. It is stored against the order. It does not tick the plan step: you read it and tick it yourself.
The run, 12 November 2026
A throwaway project, two orders from its launch plan, real workers on the other end. Nothing was posted or published.
Next Big
A research order for the throwaway project
The worker claimed the order, created the project on its side, researched it and finished. The test site had no competitors worth keeping, so the report said exactly that, and said pricing had not been collected. It did not invent any.
ppl.studio
A launch-video order for the same project
The worker created the project, ran the free launch preset on the product page and returned three cuts: 9:16, 16:9 and 1:1. The run cost one cent. It posted nothing, because accounts, phones and posting are founder steps; the result listed them.
marketinque
The console afterwards
Both orders showed as done on the first attempt, with the summaries, the cost and the founder steps beside them. The plan steps stayed unticked until a person ticked them. Then the project was deleted, with its orders and its log.
What cannot happen without you
Guarantee
A worker only sees its own kind
Each worker holds a key that can do one thing: list, claim and report orders of one role. It cannot read the plan, request orders, or touch another worker’s queue. A research key cannot claim a content order, and the test suite checks that it fails.
Guarantee
Workers never approve and never spend
Approving an order that needs money, setting a budget and cancelling are founder-only actions behind the operator login. Paid work waits for a yes, or draws on a monthly budget you set, and each of those decisions is written to a tamper-evident log.
Guarantee
A result never completes a step
Only a person ticks a plan step. A worker that returns a wrong or empty result cannot make the plan look finished.
Guarantee
The same request twice is the same order
Asking again for a step that already has a live order returns that order. Completing an order twice returns the stored result. A stale claim from an earlier attempt is refused.
What it does not do yet
- Results do not yet flow back into the plan as signals (a competitor gap that reorders the SEO steps, for example).
- Outreach, meaning direct messages and replies, is not an order type. It is run by separate routines and is tracked outside marketinque for now.
- A paid film path, where the first preview is free and the full render waits for approval, is designed but not switched on.
- Orders are created by a button, not automatically when a step unlocks. That is a deliberate choice for now.
Questions
Can I use Next Big, ppl.studio or Control Center today?
Not yet. They run on the founder’s own computers and are marked coming soon. marketinque itself is live: the plan, the approvals, the log and the launch tools work without them, and the loop on this page is what it will do once they open up.
Why does the worker pull instead of marketinque sending the job?
Because then no worker needs an open door. It reaches out, asks for work, and reports back. If it is off, asleep or broken, orders wait in the queue and nothing is lost.
What stops a worker spending money or posting something?
Its key cannot. Spending and approval are founder-only actions, and posting is not an order type at all. The worker can make and report; a person decides what leaves.
What does a work order contain?
The product name, its web address, the step it came from and the role it needs. It carries no passwords, keys or payment details.
What happens when a worker fails?
It reports the error and whether a retry makes sense. A retryable failure puts the order back in the queue, up to three attempts. After that it stays failed and shows as an alert for the founder.
Point the loop at your product
marketinque is live today: paste your URL and it plans the launch. The engine behind it is described step by step, and the tools above join it as they open up.