Buyer research you can point a campaign at
Personas with a job, a fear and a calendar, not a stock photo and three adjectives.
Maestrix turns research into stored persona objects. Any later task can be written for a specific persona, so the copy stops sounding like it was written for everyone.
Most personas are decoration
They get made once for a workshop, they describe a demographic instead of a decision, and no writer ever opens them again.
- Copy addressed to an average reader who does not exist
- No language taken from how buyers actually talk
- Objections discovered on sales calls instead of before them
Tasks you can run here, and what they deliver
Every run reads your Marketing Brain first. One credit each, exports included.
What the brain contributes to every run
Stored objects go in, sharper objects come back out. Nothing starts from a blank prompt.
Reads from your brain
- Project brief and product capabilities
- Existing use cases and proof points
- Positioning and the segment you chose to win
- Competitors buyers are comparing you against
Writes back after the run
- Persona objects reusable in every later task
- Audience insight notes per segment
- Objection library with your answers
- Journey stages that content planning reads from
A look at the output
An excerpt from a real run, shortened for the page.
The job
Show pipeline contribution this quarter with a team of four and no new headcount approved until the next board meeting.
The fear
Being seen as the department that produces content nobody attributes revenue to. Budget conversations already reference AI doing it cheaper.
Buying trigger
A quarter where output went up and qualified pipeline did not. Usually surfaces two weeks after a board deck.
Words they use
"Pipeline coverage", "attribution", "we are drowning in drafts", "I need something defensible".
The order it runs in
Strategy first, assets last. Each step feeds the next.
- 01
Project brief
Maestrix reads your site and drafts the business context.
- 02
Personas
Who buys, what they fear, what triggers the search.
- 03
Use cases and objections
What you are hired for and what blocks the yes.
- 04
Assets
Ads, emails and pages generated for a named persona.
Why teams run it here
Reusable, not disposable
Personas are objects other tasks read, not a one-off document.
Language, not demographics
You get the phrasing that segment uses, ready to paste.
Objections handled early
The blockers arrive before the sales call, not during it.
Questions people ask
Run it against your own brand
Give Maestrix your site, get the first artifact back in minutes, and keep it in the brain.