PromptBase
Upgrade
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
Chat - (gpt-5.5)
Token size
754
Example input
[SAMPLE_1]: I've been building SaaS products for 12 years now and if there's one thing I've learned it's this: most teams overthink their onboarding. You don't need a 7-step wizard with tooltips and progress bars. You need one clear 'aha' moment in the first 60 seconds. When we redesigned our signup flow last quarter we stripped everything back to a single text box and a button. Signups went up 40%. Not because we added anything — because we removed everything that wasn't the core action. I see teams agonizing over color choices and microcopy while their users are just trying to figure out what the product actually does. Stop polishing the frame and make sure the picture is worth looking at. [SAMPLE_2]: We killed our weekly all-hands last month. Just deleted the calendar invite. No announcement, no replacement, nothing. You know what happened? People started talking to each other. Actually talking — Slack messages turned into quick calls, quick calls turned into decisions, decisions stopped waiting for Tuesday at 2pm. The all-hands had become this weird ritual where everyone sat muted while one person shared slides they'd already seen. I'm not saying meetings are bad. I'm saying default meetings are bad. If you can't explain why this meeting needs to exist this week, kill it. Your team will figure out how to communicate. They're adults. [SAMPLE_3]: Here's a hiring mistake I made three times before I learned: I hired for enthusiasm instead of attention to detail. Enthusiastic people interview incredibly well. They're excited about your product, they ask great questions, they make you feel like you've found a gem. Then they start and the typos appear. The follow-ups get forgotten. The little things that make a product feel polished start slipping. I'm not saying don't hire enthusiastic people. I'm saying enthusiasm is table stakes now — everyone shows up excited. Screen for the boring stuff: do they reply to emails within 24 hours? Do their documents have consistent formatting? Do they double-check their work before showing it to you? That's the stuff that compounds. [NEW_TOPIC]: Why we decided to go remote-first
Example output
Phase 1: Style Analysis Sentence Structure Across the 32 sentences, the average length is about **10.6 words**: 21 are short, 11 are medium, and none exceed 25 words. The rhythm deliberately alternates between compact declarations such as “Signups went up 40%” and longer causal sentences that explain the lesson. Openings are usually subject-first—“I’ve been building,” “We killed,” “Enthusiastic people interview”—with occasional fragments used for emphasis. Questions are rare but strategically placed, as in “You know what happened?” Vocabulary The vocabulary is simple, conversational, and grounded in ordinary workplace language. Domain terms such as “SaaS,” “onboarding,” “microcopy,” “Slack,” and “table stakes” appear, but they are never defined or allowed to dominate the piece. The author favors forceful, concrete verbs: “killed,” “deleted,” “stripped,” “slipping,” and “compounds.” Casual modifiers such as “weird,” “boring,” “actually,” and “just” keep the language from sounding corporate. Tone and Voice The voice is casual but authoritative, with confidence coming from direct experience rather than credentials alone. Narrative distance is extremely close: all three samples rely heavily on “I,” “we,” “you,” and “your.” The author speaks to the reader as a peer while still issuing blunt instructions such as “kill it” and “Screen for the boring stuff.” The emotional register is mildly frustrated and urgent, but controlled rather than angry or theatrical. Structural Habits Each sample is presented as a single uninterrupted paragraph containing 8 to 12 sentences. There are no headers, subheaders, bullets, or numbered frameworks inside the pieces. Transitions are often abrupt, using fragments such as “Actually talking” or “Then they start and the typos appear.” The underlying structure is consistent: personal observation, concrete example, mistaken conventional behavior, sharper interpretation, and a direct closing lesson. Signature Patterns The clearest recurring device is contrastive correction: “I’m not saying meetings are bad. I’m saying default meetings are bad.” Short fragments are also used to create emphasis after a longer setup, including “They’re adults” and “The follow-ups get forgotten.” The samples contain three em dashes and four rhetorical questions, but no semicolons or exclamation marks. Metaphors are simple and visual, such as polishing a frame before checking whether the picture deserves attention. Things Consistently Avoided The author avoids academic language, elaborate theory, and long chains of qualifications. There are no citations, statistics without immediate context, formal conclusions, or corporate phrases such as “leverage synergies.” Exclamation marks, semicolons, parenthetical asides, and decorative description are absent. The writing also avoids soft endings: every sample closes with a firm judgment, instruction, or compressed principle. Phase 2: New Content We did not become remote-first because everyone wanted to work in sweatpants. We did it because the office had started making our decisions worse. Half the team was in the room. The other half was a face on a screen, waiting for someone to remember they existed. You could feel the gap. Side conversations became context, context became decisions, and those decisions showed up later in Slack with no explanation. We kept calling it hybrid. It was really two companies.So we tried fixing the office. Better cameras. More meeting rooms. Rules about opening laptops and pausing for remote people. None of it solved the real problem. The room still had gravity. People sitting together moved faster, heard more, and built trust in ways everyone else had to chase. How do you make work fair when location keeps deciding who gets the full story? You stop treating the office as the center.Remote-first does not mean remote-only. We still meet in person. We still like whiteboards, dinners, and conversations that run longer than planned. But the work has to survive without them. Decisions get written down. Meetings need a reason. Important conversations happen where everyone can join, not wherever three people happened to grab coffee. The default changed — and that changed everything else.The biggest surprise was not flexibility. It was clarity. Once we could not rely on overheard conversations, we had to explain what we meant. Once managers could not watch people work, they had to define what good work looked like. Once proximity stopped being a shortcut, ownership became easier to see.This was not a culture perk. It was an operating decision. We wanted one company, not an office team with remote guests. So we built around the people who were easiest to forget. Everyone else benefited too.
🤖 GPT

Style Mimic Write In Any Authors Voice

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
GPT-5.5
Tested icon
Guide icon
4 examples icon
Free credits icon
Match any author's voice with forensic precision. This prompt first analyzes three writing samples across six dimensions—sentence patterns, vocabulary, tone, structure, signature phrases, and avoidances—then generates new content that reads as if the original author wrote it. Great for ghostwriters managing multiple client voices, content teams scaling a single brand tone, or anyone documenting what makes a writer sound like themselves. Works on blog posts, articles, speeches, reviews, fiction, and more. The analysis output doubles as a brand-voice playbook.
...more
Added 3 days ago
Report
Browse Marketplace