Early concept · The campus journal below is an invented example, not a customer.

For people building a small website from someone else's material

Know what belongs on each page.

You were handed one long document and a bunch of images. ClientReady sorts that material by page and section, asks only about what is missing, and keeps the decisions that still need a conversation visible.

Request early access See a sample handoff ↓

It will not make anyone reply faster. It will make the one message you send specific: not “we still need content,” but “we need two bios and a confirmed opening date.”

From a folder of material to a page plan

The campus journal · one sample project, input to handoff

What arrives

Input · one long document

“We started the student journal last spring. We publish writing and visual work. The open call is in October. There are six people on the team…”

Plus a shared image folder

cover.jpgteam.jpgposter.png

The material exists. Where it goes is still unclear.

What to ask

Questions tied to a page's purpose

What should a first-time visitor know?

We publish student writing and visual work.

For the Home page introduction

What should that visitor do next?

View the open call.

For the main link on Home

Who is behind the journal?

Six students. Names and bios still needed.

For the About page

What goes where

A page-by-page handoff

HOME / INTRODUCTION

A student journal for writing and visual work.

Draft to review

HOME / MAIN LINK

View the open call · use poster.png

Confirm the opening date

ABOUT / OUR TEAM

Use team.jpg. Add a short bio for each person.

Bios still needed

Who this is for

Quotes are from our interviews (translated) and public forum posts

You're building a site for a friend or a client

“I had to work out what belonged on the homepage and what we didn't need.”

They said the content was ready. What arrived still needs selecting and placing. Start from what they sent.

One long document and a bunch of images →

You're assembling a group's writing into one site

“If the tool could tell everyone roughly what each section needs, that might help.”

Four people, one shared doc, and nothing matches. Give each section a short brief before anyone writes.

Tell everyone what each section needs →

You keep an event or club page up to date

“It might help me see what's missing, but if they don't reply I still have to chase them.”

One view of each page: drafted, needs review, missing, waiting on a decision. The chasing stays yours, but it gets specific.

See what is still missing →

You build client sites for a living

“I send clients a simple questionnaire before starting… Then I rewrite it into proper web copy.”

Keep the client's words beside your draft, assign their images to sections, and flag the facts only they can confirm.

Start from what the client already sent →

What it does, and what it doesn't

Starts from the material you already have. A document, a folder of images, a chat thread. No one has to retype anything into a new tool first.
Asks short questions, only where something is missing. Each question is tied to a page and a section, with an example of how much detail is useful.
Hands you content organized by page. Section text, the image that goes with it, where it came from, and what is still undecided.
Keeps people in control. Suggested placement is a suggestion. The contributor confirms the meaning; you decide what is usable. Silence is never treated as approval.

Honest limits

If a shared document already works for your team, keep it. ClientReady is meant to live alongside the doc first and earn its place.

It does not write your business for you, and it does not make an unresponsive person respond. It organizes what exists and names what doesn't.