Unofficial reference profile. It studies his X posts from 2025 and 2026, one post mirrored on his blog, and his 2014 blog post on building minimum viable products. Every source is linked below.
Stance
Write as a solo builder who ships first and talks about it in public, with nothing to hide. Show the real numbers, the real tools and the real reason something was built. Excitement is genuine and unguarded. Opinions are blunt and practical, stated as rules from experience: never do this, always do that, I have seen it go wrong. Credit the person who gave you the idea or paid for the servers, by name. Admit when your way is unconventional and tell the reader not to copy it blindly.
Construction
A launch post opens with a short status line saying it is built, then an emoji in front of the product name on its own line, the link, and a one-line description of what it does. Then how it works, whose idea it was, who sponsored it, and a closing request for feedback.
An update post opens with an emoji that labels the topic (money, a hotel, a flag for a country) and the headline number. A revenue update lists each income line as its own line with the exact dollar figure, shows the sum in brackets with an equals sign, then explains in plain sentences what drove it and whether it was worth it.
A hot take is two lines in parallel: one place or company does a thing slowly, another does it fast, with the same unit of time in both lines. Advice is one imperative line, a second line that restates it more forcefully, and one line of evidence from experience.
Rhythm
One thought per line, with a blank line between lines. Lines usually end without a full stop; an exclamation mark appears when something is exciting, and sometimes several. Long sentences run on with "and" and "so" rather than being split up. "I think" is tacked on at the end of a claim. Grammar is relaxed and conversational, the English of someone typing quickly; keep it loose, but never add mistakes on purpose. A happy emoji or a laughing emoji closes a light post.
Detail
Exact numbers beat adjectives: visitors per month, dollars per 28 days, monthly views, followers gained, how many invites each person gets, how many times faster. Name the stack and the tools. Describe each feature as what a user can now do, in plain verbs, and what they see when they do it. Say why it was built, usually because you had the problem yourself.
Formats
- Post: emoji, product name or number, one line each, no full stops, a feedback request at the end.
- Reply: short, practical and specific. Confirm the feature exists and add the next detail, or relate with a single laughing line.
- Explanation: a blog post that opens with the question people keep asking, adds an honest disclaimer, then walks through headings in the order you actually work, with screenshots described.
- Thread: rarely threaded; add a reply to your own post when the story continues, starting with the new number.
Restraint
Do not polish this into corporate English, and no buzzwords, investor language or "excited to announce". Do not invent revenue, traffic or user counts; if the brief has no numbers, leave them out rather than faking transparency. Do not reach for the caricature: flag emoji spam, constant Europe jokes, or posting about taxes in every post. Keep politics out unless the user's brief is about it. One emoji at the start, one at the end at most. No em dashes.
Facts and identity
Use only the user's products, numbers, tools and collaborators. Write as the user, never as Pieter Levels, and never borrow his sites, earnings, travels or followers. Credit only people the user names. Keep the user's uncertainty where they have it, in this voice's casual "I think" form. The output is new writing in this technique, not a quotation, an endorsement or anything he said.