The compounding loop.
What sits at the centre of Refolded is one short loop — capture, re-fold, sequence, compound. If the loop compounds, the replies do. This note explains the loop, what each station ships today, and where the surface still has gaps.
The loop, four stations
Memory → draft → track → compound.
The four stations below are the ones every lap visits. They map to four parts of the app — two of which already ship surfaces, one ships its data model, and one is the loop's name for what happens when a reply lands back in the capture station.
A meeting, a slack thread, a decision — typed or pasted. The unit of memory is small and dated.
Draft a cold or warm opener from one memory entry. Re-folding forces the draft to cite what it knows.
Test two openers against each other, then open an experiment to see which arm earns the reply.
A reply lands. The reply itself becomes a memory entry, and the next draft reads from both old and new.
A lap in real time
What one lap looks like.
Three paragraphs, one working week. Each one ends on the route the next lap starts from — and each reply rewrites the next draft.
01 — Tuesday
02 — Friday morning
03 — Monday
Why “compounding”
Not a sequence.
A loop that rewrites itself.
The pitch for a sequencer usually says: write step one, write step two, write step three. The product is a single forward flow. Refolded is not that product — there is no fixed forward flow because every reply rewrites the next lap's draft. The loop closes on memory, not on send.
That changes what gets optimised. The obvious metric on a sequencer is send volume; the obvious metric on Refolded isreply-rate-per-lap. Lower send, higher reply, faster compounding. The pricing ladder widens exactly where the loop widens — more memory, more sequences, more seats to share the loop with.
Where the gaps still are
Honest between today and the roadmap.
A founder note that flatters itself is useless to a buyer. The list below names what ships today and what is on the engineering bench — including the things this page is quiet about on purpose.
Today
- Native integrations — no live SMTP / CRM sync yet.
- Outcome capture — the experiment ledger is live; replies still enter the loop manually.
- ESP warmup — Refolded sends nothing by itself, so warmup is not its job.
- Reply detection — manual; the memory is updated when you paste the reply.
On the engineering bench
- /experiments/[id] — the per-experiment arms view is live; richer outcome capture is next.
- Native Gmail and Outlook capture — meeting, thread, decision in one tap.
- ESP warmup plugs — so the sequence surface can ship without punishing the inbox.
- Forwarded-memory handoff — paste an Instantly sequence into Refolded and have it indexed.
The FAQ page will track each roadmap item with the date it ships — for now this founder note is the canonical source.
What you'd pay for it
Same loop, three ladder rungs.
Every plan ships the full loop. The ladder widens capacity, integrations, and team seats — not the loop itself. Prices match the page that runs this site's billing.
Run one lap.
The fastest way to feel the loop is to capture one memory today and re-fold it into a draft this week. If you'd rather watch first, the waitlist is the best place — you'll see each station ship in turn.