Built for teams ordering content by the hundred.
Five stages, and a human editor standing between the draft and you. Here is each one, including the parts we would rather you learn now than discover later.
You describe the order
Import a spreadsheet or type the articles in. 1–100 per order, one tier for the whole order.
A row is a title, a main keyword and whatever else you want to pin down — length, tone, links, images. Anything you set once at the order level flows into every article and stays editable per article.
We pre-fill voice, audience and secondary keywords for each row, and mark every cell with where its value came from. Suggestions are starting points; a cell you touch is never overwritten, and nothing about a suggestion can block you from confirming the order.
How SOC 2 audits work for small SaaS teams
soc 2 compliance- Voice
- Practical explainersuggested
- Audience
- Engineering leadssuggested
Choosing a CI/CD provider
ci cd tools- Voice
- Buyer's guideedited
- Audience
- Platform teamsedited
You confirm the list and pay
Lemon Squeezy, LLC handles checkout. The price is fixed at that moment.
You see the whole table and the total before anything is charged. The price per article is captured onto the order when you pay, so a later change to our pricing has no effect on an order already placed.
Payment is what puts the articles in front of writers. Until a writer picks one up you can still cancel it for a pro-rata refund at the price you paid — the refund policy spells out exactly when that applies.
Writers claim and draft
Approved writers work in parallel, holding up to 10 articles at a time.
Your articles go to a board of vetted freelance writers, who claim what they can produce and draft to the brief you set. Because several people work one order at once, a large order does not take proportionally longer than a small one.
A claim is held for 5 hours. If it lapses the article returns to the board with the draft intact for whoever takes it next, so a writer going quiet costs you a queue position, not the work.
Writers see your website and your brief. They never see who you are.
An editor approves every article
This is the gate. Nothing reaches you that an editor has not passed.
A human editor reads each submission against your brief, checks the images are credited and the keywords are actually used, and measures the length against what you asked for. They approve, fix it themselves, or send it back to the writer with notes.
Until that happens you see a state, not a manuscript — an article sits at In editing and becomes readable the moment it reaches Ready for your review.
Not what you wanted? Send it back with a note. 2 revision requests per article are included on every tier, and a revision goes through a writer and an editor again, not straight back to you.
- How SOC 2 audits work for small SaaS teamsComplete
- Choosing a CI/CD providerReady for your review
- Reconciling cloud spend at month endIn editing
- A guide to Postgres connection poolingBeing written
- What teams get wrong about on-callWaiting for writer
Delivered where you work
A Google Doc, clean HTML, or posted straight to your WordPress site.
Approved articles arrive in the format you chose per order or per article. Up to 4 images per article are placed and credited in the body, or 5 on Plus. Standard runs to 3,500 words; Plus has no word limit and adds WordPress posting.
An approved article you leave alone finishes on its own after 5 days, so an order does not stall on your inbox. You can also mark articles complete yourself the moment you are happy with them.
How SOC 2 audits work for small SaaS teams
Photo by A. Wanjiru · CC BY 2.0 — credited automatically
Auto-posting finalizes fast
WordPress auto-posting is optional, and turning it on changes the rhythm of the whole order.
For an article to reach your site automatically, it has to be finished automatically. On auto-post orders each article is marked complete about 30 seconds after the editor approves it, and the post appears in WordPress as a draft or published, whichever you chose.
That window is too short to request a revision through us. Changes after that happen in your WordPress drafts instead. We ask you to accept this explicitly at checkout rather than bury it — it is a real cost of the convenience, and the alternative is simple: leave auto-posting off, take delivery as a Doc or HTML, and keep your 2 revisions.
Everything else is unchanged. The same writers, the same editor approval, the same screening — auto-posting only moves where the article lands and how quickly it is considered done.
Every deadline on the page
Nothing here is hidden in a settings panel. These are the timers the product actually runs on.
- 5 hoursA writer's claim
- Then the article returns to the board, draft intact.
- 3 hoursRevision pickup
- How long a revision request waits for a writer before it is offered more widely.
- 5 daysApproved → complete
- An article you never get round to finishes on its own.
- ~30 secondsOn auto-post orders
- Approval to complete, with the post going live in WordPress.
Start with 1 article or 100.
Upload a spreadsheet, confirm the details, and let the pipeline run.