Writing samples

Read the writing before you hire us.

We don’t publish client work; that’s the point of ghostwriting. So we wrote these four pieces for this site, each from a fictional brief, to show how we handle voice, story, structure and plain explanation.

Demonstration material. Created for this site. These are not client projects, and no results are implied.

01

Founder perspective

Demonstration piece

The brief (fictional)

A scheduling-software founder explaining a focused product roadmap to customers and the team.

Adding chat would make our product look more complete. It would also give customers another inbox to check. For now, we’re leaving it out.

We’re building a scheduling tool for people who need to know who is working, where, and when. A feature belongs on the roadmap when it makes that job easier. A chat window might help someone ask about a shift. Clear shift details might remove the need to ask.

When a request comes in, I want us to understand what prompted it. Sometimes the right response is a new feature. Sometimes it’s a clearer screen or a better default. That judgment is part of the work, even when it leaves less to announce.

Craft note

A specific product decision gives a candid founder voice something concrete to argue.

02

Website service copy

Demonstration piece

The brief (fictional)

A neighborhood furniture workshop helping owners decide whether to ask about a repair.

A loose chair leg. A drawer that sticks. A cabinet door that never quite closes. We repair wooden furniture and help you decide what’s worth doing.

Start by sending clear photos of the whole piece and the damaged area. Tell us what changed and whether anyone has tried to fix it already. We may need to see it in person before we can explain the repair.

From there, we’ll talk through the work, the finish, and the cost. Some pieces need a small adjustment; others need more than you may want to spend. You decide whether to go ahead after you understand the options.

Send photos of your piece to get started.

Craft note

Familiar problems lead to a manageable first step, followed by a clear explanation of the customer’s decision.

03

Technical clarity

Demonstration piece

The brief (fictional)

A software team explaining reliable form behavior to a client who does not write code.

Clicking Submit starts a request. It doesn’t tell you whether the request arrived.

Your browser sends the form’s contents to a server, which checks the information and decides whether to accept it. The connection might drop. A required detail might be missing. The server might be unable to save the entry.

If the page shows “Success” as soon as you click, it can tell you the job is done while the request is still traveling—or after it has failed.

The form should show “Sending…” while it waits for confirmation. It can show success after the server accepts the submission. If something goes wrong, it should explain the problem and keep your answers so you can try again without starting over.

Craft note

The explanation follows the submission from click to confirmation and connects each technical step to the user’s experience.

04

Book & memoir

Demonstration piece

The brief (fictional)

A retired boat mechanic in his sixties wants to write a memoir about the last summer of his father’s boatyard, for his grandchildren first and for a wider audience if it finds one. The narrator, his family and the boatyard are invented for this demonstration.

Opening of chapter one

My father sold the boatyard on a Tuesday, which annoyed me even then, because Tuesday was the day we hauled boats.

I was sixteen. I had spent that morning under the hull of a twenty-six-foot cabin cruiser called Second Wind, scraping barnacles with a putty knife and a bucket of water that had gone warm by nine o’clock. Her owner came down every Tuesday to watch us work and tell us how his last mechanic did it. My father let him talk. A man who pays the bill gets to tell you what he’d do, he said, as long as he doesn’t try to do it.

The buyer arrived a little after eleven in a clean white pickup. He didn’t get out right away. He sat with the engine running and looked at the yard the way you look at a used car you’ve already decided to buy: not at what was good about it, but at what it would cost to fix. The rail that ran down into the water. The shed roof, patched in three colors of tin. The pile of old propellers by the fence that my father said he would sort one day.

My father wiped his hands on the red rag he kept in his back pocket and walked over. They talked for maybe ten minutes. I couldn’t hear them over the radio, and I didn’t turn it down, because I thought that if I didn’t hear it, it wasn’t happening.

When the truck left, my father came back and crouched beside me under Second Wind. He looked at the hull for a long time.

“You missed a spot,” he said, and pointed.

I had. I scraped it. He watched me do it, and then he told me the yard would close at the end of August, that the man in the truck wanted the land and not the business, and that he would tell my mother at supper, so I should let him be the one to say it.

That was the whole conversation. I have thought about it for almost fifty years, and I still can’t tell you whether he waited until I’d fixed the spot so that I would finish the job, or so that he would have something to look at while he said it.

We put Second Wind back in the water that afternoon, same as any Tuesday.

Proposal hook

The summer a sixteen-year-old learned his father’s trade was the summer his father sold it. A memoir about work, inheritance and the things fathers say while looking at something else.

Craft notes

  • Voice in the first line. “Which annoyed me even then” sets a dry, plain-spoken narrator before anything happens.
  • Detail carries the feeling. The putty knife, the warm bucket and the patched tin roof do the emotional work, so the narrator never has to name it.
  • Control of the news. The sale arrives in one reported sentence, and the excerpt returns to the day’s work after the news.
  • An honest distance. The older narrator admits what he still doesn’t know, which is what makes memoir trustworthy.

Want writing like this under your name?

Start with a few sentences about the project. We reply with questions, then a proposed scope, delivery date and quote.