How to build a Threads post bank
Nobody quits posting because it was too much work. They quit because at eight in the morning the box is empty and they have to invent something, and one day they don't.
The short version
- The blank box is the enemy, not the writing. A post takes four minutes; deciding what to post takes forty.
- Write in batches. Fourteen posts in one sitting takes about ninety minutes. The same fourteen written one a day takes closer to five hours.
- Work from types, not topics. Filling a known slot is a different, much easier task than inventing a post.
- Collect all week, write once. The raw material is questions, numbers and changes of mind, not inspiration.
- Keep a spare shelf of four or five evergreen posts for the week that goes wrong, because one will.
What a post bank is
A written, ready-to-post stack of ten to twenty posts, produced in one sitting, that you draw from daily. It exists to move the decision about what to say away from the moment you have to say it, which is the moment you are worst at making it.
The unglamorous truth about consistent accounts is that almost none of them are run by people who are more disciplined than you. They are run by people who removed the decision. Posting from a bank is a two-minute job: open the note, take the top one, paste, post. Posting without one is a creative act performed on demand, daily, forever, and nobody sustains that.
This is also the reason batching produces better posts rather than worse ones. Writing fourteen at once means you cut the four weakest, which you cannot do when you are writing one and it is nine in the morning and it has to go out.
Why the daily decision is what kills accounts
Because it is a fresh, unbounded, creative problem presented at the worst possible time of day, every day, with no deadline pressure to force it. Skipping it costs nothing on any individual morning, which is exactly why it eventually gets skipped permanently.
| What people think stops them | What actually stops them |
|---|---|
| Running out of ideas | Having ideas but no format to put them in |
| Not enough time | Twenty minutes of deciding for a four-minute task |
| Low reach | Reach that never compounds because posting is irregular |
| Not being interesting enough | Writing while tired, unprepared, and under time pressure |
Every row on the right is fixed by the same thing. A bank turns writing into a scheduled task you do once a week when you are actually in the mood, and posting into an errand.
The twelve post types
A fixed rotation of formats you fill in rather than invent. When the type is decided in advance, writing a post is a small, bounded problem, and the account stays varied without you having to think about variety.
| Type | What it is for | Shape |
|---|---|---|
| Opinion | Replies, which drive reach | A claim someone could argue with, then one line of why |
| How-to | Follows and saves | Three to five concrete steps, no preamble |
| Mistake | Trust, fast | Something you got wrong, what it cost, what you do now |
| Number | Credibility | One real figure from your own work and what it means |
| Story | The trust that makes selling possible | One moment, one specific detail, one lesson |
| Question | Next week's material | Something you actually want answered |
| Contrarian | Reach, occasionally a lot | The common advice, and why it fails in a specific case |
| Behind the scenes | Follows from people who are building too | What you are working on today, concretely |
| Resource | Saves and bookmarks | A tool, a link, a template, and why it earns its place |
| Reframe | Shares | The same problem, described in a way that makes it solvable |
| Progress | Repeat readers | Where a thing stands versus last month |
| Offer | Sales | One post in five, tied to the four before it |
Twelve is deliberate: enough that a week never repeats a shape, few enough to hold in your head. The one type people underuse is mistake, because it feels like a bad look. It is the fastest way to be believed, and it costs nothing.
Where the raw material comes from
From the week you already had, written down as it happens. Nobody produces fourteen good posts from a blank page on a Sunday; they produce them from a note that already has twenty fragments in it.
- Questions people asked you: in DMs, replies, at work. A question asked twice is a post, and a question asked five times is a product.
- Numbers from your own week: a reply rate, an hour saved, a price you changed. Specific figures are the difference between a post and a platitude.
- Things you changed your mind about: the most under-used material anyone has, and it always outperforms.
- Posts that worked for other people: the structure, never the words. What made it land, applied to something you actually know.
- Your own replies that got traction: already tested in front of someone else's audience, which is the point of the reply strategy.
- The thing you were about to say out loud: the sentence in your head when you read something annoying is usually the post.
One note, not a system. A single file on your phone that you dump fragments into beats an elaborate content database, because you will actually open it. The bar for adding something is one line, not an idea.
Writing a week in one sitting
- Open the note and read it end to end (5 min). Do not write yet. You are looking for which fragments have something in them.
- Assign types (10 min). Match fragments to slots: this one is a mistake post, that one is a number. Fill gaps with types you have not used lately.
- Write fast and badly (45 min). Fourteen drafts, no editing, no deleting. Momentum is doing most of the work here.
- Cut the first line of every one (15 min). If the post still makes sense without it, the line was throat-clearing. It usually was.
- Kill the worst four (10 min). You now have ten you would actually send, which is more than the fourteen you would have written one at a time.
- Put the offer post in (5 min). One in five, and it should be the conclusion of the ones around it rather than an interruption.
Ninety minutes, once a week. The number that matters here is not the ninety. It is that on the other six days the posting decision does not exist.
The first line does all the work
Threads truncates, and the reader decides in about a second. The first line has to carry the claim, the number or the tension. Context, setup and “I've been thinking about…” all belong in the second line, if anywhere.
| Weak opening | What it should have opened with |
|---|---|
| “I've been thinking about pricing lately…” | “I doubled the price and sales went up.” |
| “Here's a quick thread about replies…” | “Ten replies a day beat a second daily post. Every time.” |
| “Something I learned this week…” | “I wasted three weeks building a feature nobody asked for.” |
How big the bank should be
| Stage | Bank size | Refill |
|---|---|---|
| First month | 10–14 posts | Weekly, ninety minutes |
| Months two to three | 14–20 posts | Weekly, sixty minutes (it gets faster) |
| Steady state | 20+ posts, plus a spare shelf | Fortnightly, plus fragments captured daily |
The spare shelf is four or five evergreen posts with no time reference in them, held back for the week you are ill, travelling, or simply out of it. Every account has that week. The ones that survive it are the ones that had five posts in a drawer.
And when a post from the bank does unusually well, do not retire it. Reach is a lottery: the people who saw it are a small fraction of the people who will be shown it next month. Rewrite the first line, change the example, and send it again in six weeks.
The system behind this, written down
Everything above is the map. The Income Loop is the work inside it: modules 0–6 from the problem you solve to the offer that pays for it, plus ten traffic paths: the deeper post banks, the content sales systems and the full software build sequence, in one place.
Get The Income LoopNot ready to pay for anything? The Basic Income Loop is free and includes a complete seven-day starter for Threads, Instagram or software, enough to find out which one suits you before spending anything.