Up to 15 client sites, kept current. One Desk.

If you run an agency, the Agency plan gives you one Hynca Media Desk account for up to 15 client websites, with 500 credits a month. Each site keeps its own voice and news feeds. Every piece is checked claim by claim, and each client approves the pieces for their own site. That's how you produce checked, client-approved content for multiple client sites without a separate account, process or inbox for each one.

The plan is built around three problems agencies tend to raise. Content retainers don't scale. Clients worry about AI making things up and putting their name to it. And approvals by email drag on. This guide takes each in turn, then covers how pieces reach the sites and the setup mistakes worth avoiding.

What the Agency plan covers

The Agency plan gives you one account for up to 15 client websites. It includes 500 credits a month.

In practice, one login holds every client site you manage, up to that limit. If you look after 8 client sites today, all 8 sit in the same account, with room for 7 more as you take on new work. You don't switch between separate logins to check what's waiting for review, and you don't keep a spreadsheet of which client is on which account.

The 500 credits a month are shared across the account. Plan how you spread them across clients the same way you'd plan any shared monthly allowance, by looking at which sites need news most often.

How each client site stays separate

One account doesn't mean one voice. Each site has its own settings:

• its own voice, so a piece reads the way that client writes
• its own news feeds, so the Desk looks for stories relevant to that client
• its own audience, so pieces are written for that client's readers
• its own language, set to UK English or US English
• for regulated clients, a compliance block

These settings belong to the site. One client's settings don't spill into another's. Say you manage a trade body and a local retailer. The trade body's pieces are written for its members, from its own feeds, in its own voice. The retailer's pieces are written for its customers. Neither borrows from the other.

Language works the same way. Set a UK client's site to UK English and its pieces use British spelling and idiom; if you also have US clients, their sites can use US English from the same account. For most agencies working with UK small businesses and member organisations, UK English will be the default, and it's worth confirming on every site you add.

For clients in regulated fields, the site also has a compliance block.

How you keep invented claims off client sites

Clients worry about AI making things up: will the Desk invent something, and will it end up on their site under their name?

Every piece is written from the source's own facts. It's checked claim by claim against those facts. The source is linked and credited in the piece, so a reader (or your client) can see where each story came from.

That gives you something concrete to tell a nervous client. Pieces aren't written from general knowledge or guesswork. They're written from a named source, and the source is there on the page.

You can also edit a piece on the Desk before it goes for approval: tighten a sentence, change a heading, cut a paragraph the client won't want. The Desk learns each client's voice from those edits. Over time, the drafts for each site need less of your attention, because the corrections you make for one client are learned for that client's site.

Editing on the Desk matters for another reason. The version you edit is the version that goes to the client for approval. There's no gap between what you fixed and what they see.

Getting client sign-off without the email chain

For an agency, this is the part that matters most. You can invite each client as an approver on their own site. They review the pieces for their site on the Desk and approve them there.

Every approval is logged with a fingerprint of the text. If a client later asks what they signed off, there's a logged approval to refer to, and you don't search an inbox for the right attachment or the right reply in a long thread.

This one step deals with two of the three problems at once. Approvals stop dragging through email, because the client approves in the same place the piece is written and checked. And the client's concern about invented claims is met by their own sign-off: they see the piece, with its source credited, before it goes anywhere, and their approval is logged with a fingerprint of the text.

Nothing is published by itself. A piece moves forward only when a person approves it. For your clients, that means nothing appears on their site that they haven't seen. For you, it means a clear line between what you prepared and what the client agreed to.

Getting approved pieces onto each site

How an approved piece reaches a client site depends on the platform.

On WordPress sites, approved pieces arrive as drafts automatically. They sit in the site's drafts, ready for someone to publish. For any other platform, you copy the piece across, or download it as Word, PDF, Markdown or HTML and add it to the site that way.

Either way, a person publishes. A WordPress draft is still a draft until someone presses publish; a downloaded file goes nowhere until someone adds it. If you manage a mix of WordPress and non-WordPress client sites, this is the one place the routine differs between them. Everything before it, from finding the story to the client's approval, is the same for every site.

Mistakes to avoid when setting up client sites

Most of the value in the Agency plan comes from setting each site up properly at the start. These are the slips that cost time later.

Leaving the language unchecked. Set each site's language to match its readers. A UK client's site should be set to UK English, so its pieces use British spelling from the first draft. Fixing "color" to "colour" by hand on every piece is time you don't need to spend.

Overlooking regulated clients. If a client works in a regulated field, check that their site has its compliance block before any pieces are written. Don't assume a client's sector is obvious from their feeds or audience settings.

Editing after export. It's tempting to download a piece and tidy it in Word or the client's CMS. Make your edits on the Desk instead. The Desk learns each client's voice from edits made there; changes made after export teach it nothing, so you'll be making the same corrections every month. Edits on the Desk also mean the version the client approves is the version you finished.

Collecting sign-off by email. Invite the client as an approver from the start. If you keep emailing drafts and waiting for a reply, you bring back the delays the plan is meant to remove, and you lose the logged approval. Set up the approver when you set up the site, not after the first slow round.

Treating all sites as one. Each site's voice, feeds and audience are separate for a reason. Take the time to set them for each client individually, even when two clients look similar. A well-set site produces drafts that need fewer edits and fewer rounds with the client.

Set up this way, each client site runs on the same routine: pieces written from the source, checked claim by claim, edited by you, approved by the client and published by a person. Nothing reaches a client's site without a person's approval.

Ready to compare plans? See the Agency plan and its monthly credits on the pricing page.