Teams and people
Team members are content profiles, never users of this system. There are no accounts for them and no second approver — you sign off everything that goes out under their name.
2 of these 2 profiles are seeded examples
Their remits are worked examples, written to show what a usable one reads like. Replace them with the real team — editing a profile clears the example mark.
People
Content is generated per person, rate budgets apply per person, and attribution reports whose voice actually books calls.
- Edit remit
Example Delivery Leadexample
Delivery Lead · Delivery · 1 channel
Remit is usable: 169 words, 5 topics. Allocation can work with this.
- Edit remit
Example Founderexample
Founder · Leadership · 3 channels
Remit is usable: 161 words, 5 topics. Allocation can work with this.
Add a person
The remit is the main act here. Everything else on this form takes a minute; the remit is the part worth thirty.
What a usable remit covers
Two things read this: angle allocation, which will not hand this person an angle outside it, and the remit-fit guard, which flags a generated variant that has wandered into someone else’s subject matter. Write prose, not bullet points — a couple of paragraphs is the right size.
- Subject matter
- What does this profile own, and what does it leave to someone else?e.g. Owns how automation actually gets deployed inside a 20-200 person operations team. Leaves pricing and packaging to the CEO.
- Stance
- What does this person argue that a competent peer might disagree with?e.g. That most 'AI transformation' projects fail on process mapping, not models, and that shipping one narrow workflow beats a platform rollout.
- Kind of proof
- What evidence do they reach for — numbers, teardowns, client stories, first principles?e.g. Build logs and before/after cycle times from real deployments. Never vendor benchmarks.
- Audience
- Who is on the other side of the post, and what do they already believe?e.g. Heads of operations at UAE mid-market firms who have already tried an off-the-shelf tool and found it did 60% of the job.
- Stay away from
- What subject matter would be wrong coming from this profile?e.g. Model benchmarks, funding news, and anything that reads as a prediction about the industry.
Teams
Grouping only. Teams shape the roster; the remit shapes the content.
Delivery
The technical proof. Owns how it actually gets built and what goes wrong.
Leadership
The market view and the commercial argument. Owns the case for doing this at all.