MAXAI
Proposal · C2-001

A week of LinkedIn posts that sound like you.

Not a content agency. An engine that holds what you know about care development and turns it into posts only you could have written. It is already built, already hosted, and there are five posts on your board.

01 · The outcome

You post consistently, in your own voice, without it becoming a job

That is the single thing this is tied to. Not "a content strategy". A board that always has something specific and publishable on it, produced in the time it takes you to read it.

5Posts already written
8.4Avg specificity /10
~4 minPer batch of six
0Auto-published

Both links in the header are live, working pages. The demo runs on the real output, not a mock-up.

02 · The problem

You know things your buyers would pay to hear. Almost none of it gets said.

Care operators and investors are making six and seven figure decisions on buildings, and the thing standing between them and an expensive mistake is knowledge you have and they do not.

The net effect. The expertise stays in your head and in client meetings, and the people about to buy the wrong building never hear from you.
03 · The solution

Two agents, kept deliberately apart

Everything hangs on three decisions, and none of them are about the writing.

1. Your expertise goes in a file, not a prompt

One file holds your positioning, your five buyer types and what each is afraid of, and the proof territory: the specific things you know that make a post credible. It was written from your own site, so it already talks about the C2 use class, Ofsted registration and pre-acquisition due diligence. Change that file and every post changes. That is where the quality lives.

2. Choosing the angle is a separate job from writing it

One agent decides what is worth saying, to whom, and why now. It never writes a word. Another writes. If one pass did both, it would pick angles that are easy to write rather than angles worth saying, and you would get competent posts about nothing.

3. A reviewer that never saw the draft being written

A separate pass reads the finished post and nothing else, scoring specificity out of ten: could a competitor have posted this? Below six goes back. It also checks nothing was invented and flags anything regulatory before it reaches you.

What it cannot do. Invent a client, a project, a figure, a date or an outcome that is not in your file. Imply a planning outcome is certain. Publish anything without you. Those are enforced, not requested.
04 · The plan

The engine already exists. Three weeks to make it yours.

You are not being asked to believe a proposal. It is built, deployed behind your site, and there are five posts on the board waiting for you.

Done · before you pay anything

Proof

Both agents built, with the cold review pass and the human gate
Your brand file written from the C2 site: positioning, five buyer types, proof territory, voice rules
Hosted on the max-ai backend behind your site, private and login protected
Five posts generated, reviewed and sitting on the board
Week 1

Make it sound exactly like you

1
You read the five posts and tell me what is off. Voice is calibrated against your reaction, not my guess.
2
Brand file tightened: the angles you would never take, the things you would never claim
3
Engine connected and live. First real batch generated with you watching.
4
First posts go out
Week 2

Tune on what actually lands

5
Read the replies. Which pillar and which buyer pulled, and feed that back into the file.
6
LinkedIn connected so approved posts publish in one click
7
A second batch, steered at whichever buyer responded
Week 3

Hand it over

8
Weekly cadence set, so the board is always full
9
You shown how to edit the brand file, which is the only thing you ever need to change
10
Walkthrough and handover, you running it
05 · The quote

What it costs

Both agents, your brand file, the review pass and the board£1,900
Hosting behind your site, LinkedIn publishing and handover£500
Total, one-off£2,400

Optional, only if you want it run rather than handed over: £350 a month for weekly batches, a first-pass review before anything reaches you, and scheduling. Cancel any time, no minimum. Claude API usage sits on your own account and runs to a few pounds a month at this volume.

Included

What it is reasonable to expect

MeasureNowAfter
Time to produce a week of postsHours, if it happensMinutes
Posts ready to publish right now05
Posts that could have come from any consultancyMostScored and rejected
Risk of an invented claim going out *RealBlocked and flagged

* The engine cannot state a client, figure or outcome that is not in your file, and the reviewer flags regulatory language before you see it. You still read everything before it publishes, which is the actual control.

06 · Straight answers

The things worth asking first

Will it sound like me, or like AI?
Read the five posts on the demo before deciding. If they do not sound like you, that is what week one is for, and the fix is the brand file rather than the tool. What stops the usual AI register is that the engine has your actual proof territory and a reviewer that rejects anything generic.
I work in a regulated specialism. What if it says something wrong?
It cannot invent a client, a figure, a date or an outcome that is not in your file, and it is instructed never to imply a planning outcome is certain. The reviewer flags anything regulatory before it reaches you, which is exactly what happened on the change-of-use post. And nothing publishes without you approving it. You should still check planning specifics against current policy, because it is your name on the post.
How much of my time does this actually take?
After week one, reading and approving. A batch of six takes around four minutes to generate and about ten to read. The work that used to be writing becomes deciding.
Why not just use ChatGPT when I need a post?
You can, and it will write you something fluent about the C2 use class that any consultancy could have posted. The difference here is that the engine holds what you specifically know, chooses the angle before it writes, and has a second pass whose job is to reject the generic version. That is the whole product.
What if I want to stop?
You own the brand file and every post on full payment. The monthly retainer is optional, has no minimum, and the build works perfectly well without it.
Can it write for anything other than LinkedIn?
The engine is built around LinkedIn today because that is where your buyers are. The same brand file drives insight articles for your site, which is a natural second phase once the voice is settled.
07 · Next steps

50% to start, 50% when you are happy

Week one begins the day the deposit lands. Invoice reference C2-001, due on receipt. Not VAT registered.

Option 1 · Bank transferNo fee · recommended
Name
Max Greenhalgh
Sort code
04-00-03
Account
37940126
Reference
C2-001
Deposit
£1,200.00
Option 2 · Card via Stripe
Deposit
£1,218.20
In full
£2,436.20

Card amounts include the processing fee so the full deposit reaches us. Bank transfer avoids it.

Kickoff checklist

This proposal, the invoice reference above, and the linked Terms of Service and Privacy Policy together form our agreement. Paying the deposit confirms your acceptance.

MaxAI · C2 Content Engine · C2-001 · 20 August 2026
Built on the Claude API. Hosted on the max-ai backend behind your site. You own the brand file and all generated content on full payment. MaxAI retains pre-existing tools, libraries and know-how.