albro-founder-brand ยท diff
git:20261002.46ac0a1 to git:20261002.d5668a9
23 added, 63 removed. Audit A to A.
---
name: albro-founder-brand
- description: "Build a founder narrative and buyer focused content plan from Scott Albro's public workshop when a startup founder needs a credible brand that creates sales conversations."
+ description: "Build a buyer-focused founder narrative, content plan, distribution routine, and revenue hook using Scott Albro's public method when a startup founder needs a credible brand that creates qualified sales conversations."
---
# Founder Brand Workshop
Based on Scott Albro's public method. Not affiliated with or endorsed by Scott Albro.
## When to use
- Use this skill when a founder needs to articulate a narrative, choose what to publish, decide where to participate, or connect personal content to qualified sales conversations. ScaleVP presents Albro's workshop and template as tools for founder story, online personality, content strategy, distribution, and revenue. The method fits an early stage company whose founder has direct knowledge of customers and a point of view on its market. If the buyer and buying context are unknown, establish those first; the story cannot be judged by general popularity. [S1][S3][S6]
-
- ## Operating procedure
-
- ### 1. Fix the buyer and the business outcome
-
- 1. Ask for the target buyer's role, company type, urgent priorities, existing alternatives, and where those people already talk to one another. Write one sentence naming the buyer and one sentence naming the commercial action the founder wants, such as qualified first meetings. Treat likes from people outside that buyer group as weak evidence. Albro places the target market beneath all four pillars and warns that an undefined audience sends founders chasing attention that will not convert. [S1][S2][S3]
-
- 2. Identify what the company must be known for to make a buyer more willing to meet, shortlist, or buy. State the desired market perception in plain language, then name the existing belief or incumbent position the narrative must shift. Reject positioning that merely makes the founder seem impressive without changing a buying decision. [S2][S3]
-
- 3. Collect raw evidence before drafting: recent buyer conversations, repeated objections, observations from building the company, customer outcomes that may be shared, and the founder's own reason for starting. Mark claims that need verification or permission. Use the founder's lived knowledge as the main input, because polished secondhand copy loses the specific experience that makes this method work. [S2][S3][S5]
-
- ### 2. Build the three story columns
-
- 4. Make a compact table with columns for customer priority, market transformation, and personal journey. For each column, capture the buyer concern, the central claim, supporting incident or evidence, distinct point of view, and what the buyer should do differently. Let themes overlap across columns; the template explicitly allows that overlap. [S2][S5]
-
- 5. For the customer priority story, describe a problem in the buyer's own terms, then offer a useful prescription. Prefer a concrete observation from a real conversation or repeated pattern over a broad claim that a market has a problem. Anonymize customers unless sharing their identity is authorized. [S2][S3]
-
- 6. For the transformation story, articulate the old approach, the emerging approach, why the change is happening, and how buyers can navigate it. Include a defensible view of who benefits or struggles. Make the story large enough to reframe the market, while tying every prediction to observable evidence or clearly labeling it as a forecast. [S2][S3][S5]
-
- 7. For the personal journey, explain the founder's relevant experience, the moment that sharpened the problem, and the commitment behind the company. Keep details that help buyers understand the founder's expertise or motivation; cut autobiography that has no connection to the buyer's world. The founder should sound like a person with a reason to lead the conversation. [S2][S3][S5]
-
- 8. Test each story for differentiation. Ask what this founder knows, has witnessed, or believes that a larger competitor could not credibly say. If the answer is a generic value statement, return to raw evidence. A contrarian angle helps only when it is earned by experience; avoid provocation designed solely for clicks. [S2][S3][S5]
-
- ### 3. Give the narrative a recognizable voice
-
- 9. Write a one paragraph narrative that connects the buyer's pain, the market shift, the founder's journey, and the company's reason to exist. Then write a short version the founder could say aloud. Use the buyer community's natural vocabulary and remove phrasing the founder would never use in conversation. Albro treats the founder's authentic personality and buyer language as part of the story, not a decorative writing style. [S2][S3][S5]
-
- 10. Name the founder's natural communication mode, such as candid analyst, practical teacher, or energetic challenger, and note two behaviors that make it recognizable. Do not invent a character for the founder to perform. If a draft requires the founder to mimic a popular creator, rewrite it in their own cadence. [S2][S3][S5]
-
- 11. Check that the core narrative can be repeated many times through new evidence and examples. Keep the main claim stable while changing the incident, format, or angle. A story that works only as a single announcement is too small to carry an ongoing founder brand. [S2][S3]
-
- ### 4. Turn the story into content the founder can sustain
-
- 12. Generate two or three initial ideas for each story column. For each idea, record the specific observation, useful insight, buyer relevance, preferred format, and a first sentence. Source ideas from customer conversations, industry discussions, news that affects the buyer, and the founder's own decisions. Do not recycle a news item without adding the founder's interpretation. [S2][S3][S5]
-
- 13. Choose writing, speaking, video, or a simple recorded conversation based on what the founder can produce naturally. When useful, start with a longer statement of the market view and break its arguments into smaller posts. Let a founder who thinks aloud dictate a rough draft. Prefer a sustainable process to a format selected because it is fashionable. [S2][S3]
-
- 14. Edit for a specific opening claim or question, a real example, and a clear implication for the buyer. Numbers, images, timely events, and strong hooks can help distribution, but they must serve a valuable idea. Reject invented numbers, confidential anecdotes, empty controversy, and content that optimizes curiosity while hiding its point. [S2][S3]
+ Use this skill when a startup founder needs to explain why the company exists, articulate a distinctive market view, decide what to publish, choose where to participate, or turn relevant engagement into sales conversations. It also supports reviewing an existing founder narrative or content plan for buyer relevance and commercial usefulness. The intended deliverable is a founder brand working plan with publishable draft content and a proposed follow-up path. [S1][S3][S6]
- 15. Set a realistic publication plan that aims for at least three useful pieces per week when capacity permits. Put dates on the first pieces, but preserve momentum if a date slips. If the schedule becomes burdensome, simplify the format or source material rather than changing the founder's voice to fill a calendar. The workshop also treats enjoyment and participation in the community as conditions for keeping the practice alive. [S2][S3][S5]
+ Albro's framework connects four pillars: story, content, distribution, and monetization, all grounded in a known target market. Begin with the buyer rather than a personal popularity goal. If the buyer is uncertain, make that uncertainty visible and produce a provisional discovery brief before presenting the strategy as ready. This skill supports founder branding, not a complete company brand redesign or general influencer growth program. [S2][S3]
- ### 5. Choose distribution by buyer presence
+ Use only the detail needed for the request. A post revision may need the story and voice rules; a full strategy needs every pillar. Keep the founder's actual knowledge and language central. The agent may organize, challenge, and edit that material, but should not fabricate experiences or replace the founder's voice with a creator persona. Deliver drafts and proposed actions within the user's scope; publishing and outreach require their own authorization.
- 16. Score possible channels against three questions: are target buyers there, does the channel fit the chosen content format, and can the founder publish and participate there without a large production team? Pick one primary channel first. LinkedIn is a likely choice for many business buyers, but the buyer's actual location determines the channel. Expand only after the first channel has a working habit. [S2][S3][S5]
+ ## Procedure
- 17. Treat distribution as participation. Identify buyer communities and relevant people to follow, connect with, and respond to. Add substantive comments that advance a discussion, and answer relevant comments on the founder's own posts promptly. A publishing schedule without community engagement leaves content isolated. [S2][S3]
+ 1. **Frame the assignment.** Read [the method's scope and evidence rules](references/method.md#scope-and-evidence). Identify the requested artifact, target buyer, buying context, and desired commercial action. State missing information as questions or provisional assumptions. Use [the output template](templates/output-template.md) to establish what the final plan must contain.
- 18. Review reactions by buyer relevance and the quality of discussion, not raw reach alone. Record which claims buyers repeat, challenge, or ask about. Feed those signals back into the three story columns and the next batch of content. Do not abandon a sound narrative after one quiet post; repeated telling is part of shaping market perception. [S2][S3]
+ 2. **Define the perception to change.** Apply [buyer and perception rules](references/method.md#buyer-and-perception). Write what buyers currently believe, what the founder wants them to believe, and why that change should help a meeting or purchase decision. Avoid reputation goals that cannot be connected to buyer behavior. [S2][S3]
- ### 6. Build the revenue hook
+ 3. **Collect the founder's raw material.** Follow [evidence and voice guidance](references/method.md#evidence-and-voice). Gather conversations, decisions, observations, relevant personal history, and shareable outcomes. Separate verified facts, founder interpretations, forecasts, and unknowns. Resolve confidential material before placing it in publishable copy.
- 19. Define a simple path from content engagement to a meeting: engagement type, ICP fit, founder follow up, qualification, and resulting opportunity. Distinguish direct inbound interest from a like or comment, and treat account level impressions as weaker signals. Follow up first with people who fit the target buyer, not every person who interacts. [S2][S3]
+ 4. **Build all three story columns.** Use [the story architecture](references/method.md#three-story-columns) and the corresponding [template fields](templates/output-template.md). Develop customer priority, market transformation, and personal journey stories, including themes, evidence, and a distinctive point of view. Allow meaningful overlap among columns. [S2][S5]
- 20. Match the first approach to the signal and channel. Reply promptly to a direct inquiry; connect or message after a relevant comment; use ordinary outbound, with a reference to the content, for weak account level exposure. Make the first note short, personal, and sent by the founder, even if a teammate manages the list and later handoff. Ask for a concrete meeting or feedback conversation rather than sending a generic automated pitch. [S2][S3]
+ 5. **Challenge differentiation and scale.** Apply [the differentiation test](references/method.md#differentiation-and-repetition). Ask what this founder can credibly say that competitors cannot. Connect practical advice to a larger market belief when warranted. Keep disagreement grounded in evidence rather than manufactured controversy. [S2][S3]
- 21. Track qualified conversations, first meetings, opportunities, and lessons from buyer responses alongside content output. If content reaches buyers but creates no meetings, inspect follow up and the invitation. If it creates attention from nonbuyers, revisit the audience and story. If there is little qualified engagement, inspect channel choice, posting frequency, and community participation. The workshop allows founders to start publishing before perfecting monetization, while its full method requires a deliberate revenue path. [S2][S3]
+ 6. **Establish an authentic voice.** Use [evidence and voice guidance](references/method.md#evidence-and-voice) to name the founder's natural style and recognizable behaviors. Draft a core narrative and a short spoken version. Read both aloud and replace borrowed creator language with the founder's own vocabulary. [S3][S5]
- ## Finished output checklist
+ 7. **Create a usable content batch.** Follow [content production rules](references/method.md#content-production). Generate two or three ideas per story type for a full plan, with an observation, buyer takeaway, format, and opening. Produce the requested drafts. Consult [worked examples](examples/worked-examples.md) for how weak claims become useful, specific content. [S5]
- - Deliver the target buyer and desired market perception; a three column story table with themes, evidence, differentiation, and voice; one paragraph and spoken versions of the narrative; and two or three content ideas per story type. [S2][S5]
- - Include the primary channel decision with the buyer presence, format fit, and publishing effort behind it; initial publication dates; a participation routine; and a revenue hook that maps engagement signals to a founder first touch and meeting request. [S2][S3][S5]
- - Flag unverified claims, private anecdotes, unsupported forecasts, and any missing buyer evidence. Keep those out of publishable copy until resolved. [S2][S3]
+ 8. **Set format and cadence.** Apply [cadence decisions](references/method.md#cadence-and-capacity). Choose writing, speaking, or video based on founder comfort and buyer context. Set initial dates, capacity, and a recovery plan. Preserve Albro's three-times-weekly recommendation while explicitly noting any capacity adaptation. [S2][S3][S5]
- ## Worked example (illustration)
+ 9. **Choose distribution and participation.** Use [channel selection rules](references/method.md#distribution-and-participation). Compare buyer presence, format support, and publishing effort. Select one primary channel and a routine for substantive comments and relevant replies, then record both in [the template](templates/output-template.md). [S2][S3]
- An invented founder sells software to independent repair shops. The buyer is an owner who loses bookings when phone calls pile up at the front desk. The customer priority story uses anonymized observations from five owner interviews and suggests a way to measure missed calls. The transformation story argues that shops will move from reactive phone handling to automated intake, and identifies the tradeoffs owners must manage. The journey story explains how the founder watched a family shop lose repeat customers during busy afternoons. Her distinct claim is that the first automation should recover missed calls before it tries to replace the service advisor. [S2][S5]
+ 10. **Design the revenue hook.** Follow [engagement and follow-up rules](references/method.md#revenue-hook). Map each signal to buyer fit, founder first touch, qualification, and a meeting invitation. Draft a short personal note without assuming a like or impression establishes buying intent. [S2][S3]
- Her first pieces are a short analysis of missed booking patterns, a post on what to automate first, and a personal account of that family shop. She chooses a trade association forum because owners already participate there and she can write brief responses. Her revenue hook is to answer relevant questions, message owners who request the intake checklist, and invite qualified owners to a short diagnostic call. This is an illustration of the method, not a claim about a real company or an expected conversion rate. [S2][S3]
+ 11. **Review and iterate.** Run [the pass/fail checklist](checklists/review-checklist.md), repair failures, and mark unresolved assumptions. Specify how qualified conversations and buyer feedback will inform the next batch. Return the requested artifact with evidence limitations and the next review point, without promising conversion results.
- ## Sources
+ ## Files in this skill
- 1. [S1] ScaleVP, Founder brand workshop, https://www.scalevp.com/resources/founder-brand-workshop
- 2. [S2] Scott Albro, The Founder Brand workshop slides, https://cdn.prod.website-files.com/692f28f1d17b8ec4f8005e36/6978d0f98d707fed606fb31a_Founder-brand-workshop.pdf
- 3. [S3] ScaleVP, Founder brand playbook, based on Scott Albro's presentation, https://www.scalevp.com/resources/how-to-build-your-founder-brand
- 4. [S4] ScaleVP, The 5 rules of founder-led GTM, Scott Albro session summary, https://www.scalevp.com/resources/the-5-rules-of-founder-led-gtm-b5aa0
- 5. [S5] Scott Albro, Founder Brand Template, https://cdn.prod.website-files.com/692f28f1d17b8ec4f8005e36/6978d0f4c88f7791537bf7cf_Founder-brand-template.docx
- 6. [S6] ScaleVP, Founder brand template resource page, https://www.scalevp.com/resources/founder-brand-template
+ - [SKILL.md](SKILL.md): Entry point, use conditions, and the agent's main loop.
+ - [references/method.md](references/method.md): Detailed principles, decision rules, warnings, and edge cases.
+ - [references/sources.md](references/sources.md): Fetched public sources and their contributions, indexed by [S#].
+ - [examples/worked-examples.md](examples/worked-examples.md): Invented before-and-after illustrations with rule explanations.
+ - [templates/output-template.md](templates/output-template.md): Fill-in founder brand plan with field guidance.
+ - [checklists/review-checklist.md](checklists/review-checklist.md): Pass/fail review and common failures with fixes.