Lapel growth playbook

Turn both buttons into real anchor links to a new, crawlable /early-access page (it can still open as an overlay as well). The page says who Lapel is for (customer-facing teams across sales, success and support), what the early-access programme involves, and asks four qualifying questions: team size, tools to connect (CRM, support, email and calendar), number of active accounts, and the biggest service gap today. Each request goes to a founder, gets a reply within one business day and includes a booking link. Give the X and LinkedIn icon links accessible names, and record each submission as a Fathom goal so the founders can see requests per week and by source. Upside: every interested visitor has a route that works everywhere, the founders get qualified requests instead of cold emails, and the brand hire starts with a measurable funnel.

Early-stage enterprise software sells on founder conversations, and every one of them starts with a visible, easy request. A real URL can also be shared in launches, essays and investor intros, and found by search engines and AI assistants.

[ ] "Early access" and "Get in touch" are real <a href> links to /early-access
[ ] /early-access loads without scripts and is in the sitemap
[ ] Who it's for: sales, success and support teams
[ ] Four questions: team size, tools to connect, active accounts, biggest service gap
[ ] Request reaches a founder with a booking link
[ ] Reply within one business day
[ ] Fathom goal on submit
[ ] Accessible names on X and LinkedIn icons
[ ] Link from careers page and social bios

• The buttons already open a form through a script

  Keep it, but give it a real URL too so it works everywhere and can be shared and measured.

• Too many unqualified requests

  Use the four questions to sort, and send a polite waitlist reply to those who don't fit yet.

• Your websiteHomepage (fetched twice, November 9, 2026): H1 "Setting a new standard for service."; "Lapel builds infrastructure to power every customer interaction on the internet."; promises "hospitality at scale"; says Lapel works with a select group of companies, from startups to enterprises. The buyer buttons "Early access" and "Get in touch" carry no link address in the page HTML, and there is no form, email address or booking link; the page's only links go to /careers, four Ashby job posts, X, LinkedIn and /privacy. No customer logos, testimonials or numbers. Page title "Lapel"; meta description "Interaction operations to support every customer touchpoint."Source
• PageSpeedHomepage, tested November 9, 2026: mobile performance 74, desktop 75, accessibility 96, SEO 92. SEO flag "Links are not crawlable"; accessibility flag "Links do not have a discernible name". Real visitors pass Core Web Vitals (Chrome UX Report p75: LCP 581 ms, INP 62 ms, CLS 0), so speed is not the problem; lab mobile total blocking time is 1,311 ms.Source
• Your websiteSitemap (checked November 9, 2026): 5 URLs in total: /, /privacy, /security, /404 and /careers. No product, how-it-works, integrations, pricing, customer, changelog, blog or docs pages, and no newsletter; social links are X and LinkedIn only.Source

Write one category sentence (what it is, for whom, and the outcome) and one three-word category name, then apply them everywhere at once: homepage H1 and subhead, page title and meta description, YC profile, LinkedIn and X bios, job-post boilerplate and the privacy policy's service description. Keep "hospitality at scale" as the belief, and make the category name the thing buyers can repeat and search for.

A new category spreads only when everyone, including AI assistants that summarise companies, repeats the same words. One name makes every later launch build on the last.

• Locking in a name too early

  Review it after the first three launches; consistency matters more than perfection now.

• Your websiteHomepage (fetched twice, November 9, 2026): H1 "Setting a new standard for service."; "Lapel builds infrastructure to power every customer interaction on the internet."; promises "hospitality at scale"; says Lapel works with a select group of companies, from startups to enterprises. The buyer buttons "Early access" and "Get in touch" carry no link address in the page HTML, and there is no form, email address or booking link; the page's only links go to /careers, four Ashby job posts, X, LinkedIn and /privacy. No customer logos, testimonials or numbers. Page title "Lapel"; meta description "Interaction operations to support every customer touchpoint."Source
• HiringHead of Brand & Content (San Francisco, posted June 9, 2026, still listed on lapel.com/careers): "Lapel is building a new category of software, and how the market understands it starts with how we talk about it." The role will "Develop and maintain Lapel's brand voice and positioning across every external surface", "Own the marketing engine across written, video, and launch formats", "Support frequent product launches with structured narratives and polished assets", "Brief and manage freelance writers, designers, and video editors" and "Operate as a close creative partner to the founders".Source
• Your websitePrivacy policy (last updated July 25, 2025): Lapel, Inc. builds software that helps internet businesses "unify customer data and automate operational workflows". Customers connect CRM, support, email or calendar and analytics tools; Lapel processes CRM records, support tickets, product usage data, communication content and recordings of sales or support calls on the customer's behalf. No subprocessor list is published. It may use de-identified or aggregated data for "training and improving models and automated systems".Source
• Y CombinatorLapel's Y Combinator company page one-liner: "Infrastructure to power every customer interaction."Source
• Site historyHomepage headline a year ago: "The internet forgot. We're helping it remember." Now: "Setting a new standard for service." (change tracked since November 9, 2025).Source

Change the homepage title to "Lapel | <category name> for sales, success and support teams" and rewrite the meta description with the category sentence. Add Organization structured data (name, logo, sameAs links to LinkedIn, X and the YC page). Use "Lapel" plus the category name in every bio and launch headline, so searches like "Lapel customer operations" and "Lapel software" find lapel.com first.

A common word as a brand name is fine once the title, structured data and profiles teach search engines and AI assistants which Lapel this is. Without them, word-of-mouth leaks to tailoring pages.

• Plain "lapel" stays a tailoring query

  Aim for "Lapel" plus a category word; that is how buyers will search.

• #2 Pick one name for the category and use it on every surface, before the brand hire inherits four

• Search resultsA web search for "lapel" (November 9, 2026) returns only suit and tailoring pages, led by Wikipedia's "Lapel" article, in the top 25 results; lapel.com does not appear.Source
• Your websiteHomepage (fetched twice, November 9, 2026): H1 "Setting a new standard for service."; "Lapel builds infrastructure to power every customer interaction on the internet."; promises "hospitality at scale"; says Lapel works with a select group of companies, from startups to enterprises. The buyer buttons "Early access" and "Get in touch" carry no link address in the page HTML, and there is no form, email address or booking link; the page's only links go to /careers, four Ashby job posts, X, LinkedIn and /privacy. No customer logos, testimonials or numbers. Page title "Lapel"; meta description "Interaction operations to support every customer touchpoint."Source

Ask current design partners for one of three levels of permission: a logo, a named quote, or an anonymised story ("a Series B developer-tools company, 40-person support and success team"). Publish three short before-and-after stories: what was scattered, what the team now sees, what they did differently. Add one honest number per story, such as hours saved per week or accounts flagged before renewal.

Early buyers mainly want to know whether teams like theirs already trust Lapel. Anonymised specifics answer that without exposing customers.

• Partners decline any mention

  Use aggregate numbers across all partners instead.

• HiringLapel's description in its job posts: "At Lapel, we believe the most hospitable companies win." It builds "the data, infrastructure, and tools that help customer-facing teams understand every customer"; "Most internet businesses want to treat customers well, but their tools work against them." "We're well-funded, backed by top-tier investors, and already working with exceptional companies," "from fast-growing startups to large enterprises." The team works in person in San Francisco.Source
• Your websiteHomepage (fetched twice, November 9, 2026): H1 "Setting a new standard for service."; "Lapel builds infrastructure to power every customer interaction on the internet."; promises "hospitality at scale"; says Lapel works with a select group of companies, from startups to enterprises. The buyer buttons "Early access" and "Get in touch" carry no link address in the page HTML, and there is no form, email address or booking link; the page's only links go to /careers, four Ashby job posts, X, LinkedIn and /privacy. No customer logos, testimonials or numbers. Page title "Lapel"; meta description "Interaction operations to support every customer touchpoint."Source
• Competitor researchRivals' own homepages: Pylon, "The new way to run customer support", "Trusted by 1,800+ B2B customers globally", with support, account and product data available to agents and teams via MCP; Vitally, an AI assistant across customer history, usage and conversations, "Trusted by 600+ Leading Customer Success Teams"; Attio, "Welcome to agentic revenue", "Trusted by 30,000+ customers", with "Universal Context" and 30M MCP tool calls a month; Gainsight, "The Customer Retention Platform", giving "your people and AI agents the context to act at the right moment".See the research Source

Publish /trust: what data Lapel reads from each connected system, where it is stored, retention and deletion, how one customer's data and agent context are kept apart (the Agents role already names multi-tenant isolation), the subprocessor list, the model-training position in plain words (including a way to opt out), and the honest status and timeline of any compliance audit. Add a downloadable security summary for procurement.

Answering security questions before they are asked shortens enterprise reviews. Being open about model training builds trust with companies that are wary of AI tools touching customer conversations.

• Saying too much about internals

  Describe policies and controls, never architecture details an attacker could use.

• Your websitePrivacy policy (last updated July 25, 2025): Lapel, Inc. builds software that helps internet businesses "unify customer data and automate operational workflows". Customers connect CRM, support, email or calendar and analytics tools; Lapel processes CRM records, support tickets, product usage data, communication content and recordings of sales or support calls on the customer's behalf. No subprocessor list is published. It may use de-identified or aggregated data for "training and improving models and automated systems".Source
• Your websiteSecurity page (updated July 15, 2026): a vulnerability disclosure policy with acknowledgement within 3 business days, fixes targeted within 90 days and no bug bounty. It lists no certifications or compliance reports, and the site has no trust centre.Source
• HiringThree backend roles (San Francisco, posted May 27, 2026). Primitives: customer records, threads, workflows, permissions and actions, an extensibility model for customers, and primitives usable by people and agents. Core Platform: systems that sync, parse, store, transform, permission and retrieve information from customers' external systems, an integration framework, and workflow infrastructure for long-running jobs and agent-driven actions. Agents: long-horizon agents that remember, retrieve customer context, use tools and take actions, with evals, observability and multi-tenant isolation for enterprise customers.Source

Publish /how-it-works in three panels: Connect (CRM, support, email and calendar, analytics), Understand (one account view built from records and threads), Act (workflows and agents that take actions, with permissions). Illustrate each panel with a stylised product view using fictional data, and end with the early-access link.

Buyers of a new category need to picture the product before they will book a call, and the product language already exists in the engineering roles.

• Revealing too much to rivals

  Show outcomes and flow, not internals.

• #2 Pick one name for the category and use it on every surface, before the brand hire inherits four

• Your websiteSitemap (checked November 9, 2026): 5 URLs in total: /, /privacy, /security, /404 and /careers. No product, how-it-works, integrations, pricing, customer, changelog, blog or docs pages, and no newsletter; social links are X and LinkedIn only.Source
• HiringThree backend roles (San Francisco, posted May 27, 2026). Primitives: customer records, threads, workflows, permissions and actions, an extensibility model for customers, and primitives usable by people and agents. Core Platform: systems that sync, parse, store, transform, permission and retrieve information from customers' external systems, an integration framework, and workflow infrastructure for long-running jobs and agent-driven actions. Agents: long-horizon agents that remember, retrieve customer context, use tools and take actions, with evals, observability and multi-tenant isolation for enterprise customers.Source
• Your websitePrivacy policy (last updated July 25, 2025): Lapel, Inc. builds software that helps internet businesses "unify customer data and automate operational workflows". Customers connect CRM, support, email or calendar and analytics tools; Lapel processes CRM records, support tickets, product usage data, communication content and recordings of sales or support calls on the customer's behalf. No subprocessor list is published. It may use de-identified or aggregated data for "training and improving models and automated systems".Source

Publish /integrations with one card per supported tool (by category: CRM, support, email and calendar, analytics), what Lapel reads, and a status (live, beta, requested). Add a "request an integration" link that feeds the early-access form, and use the requests to prioritise the roadmap.

Named integrations answer the fit question instantly, rank for "<tool> + account view" searches, and turn missing connectors into demand data.

• Listing tools that partially work

  Show honest beta labels.

• Your websitePrivacy policy (last updated July 25, 2025): Lapel, Inc. builds software that helps internet businesses "unify customer data and automate operational workflows". Customers connect CRM, support, email or calendar and analytics tools; Lapel processes CRM records, support tickets, product usage data, communication content and recordings of sales or support calls on the customer's behalf. No subprocessor list is published. It may use de-identified or aggregated data for "training and improving models and automated systems".Source
• HiringProduct roles (posted June 9, 2026): a Product Designer for zero-to-one concepts and the design system, a Design Engineer taking interfaces from Figma to production React/TypeScript with attention to performance and accessibility, and a Product Engineer to "Design and implement APIs, services, and integrations". lapel.com/careers also lists a Talent Lead and invites candidates to propose their own role.Source
• Your websiteSitemap (checked November 9, 2026): 5 URLs in total: /, /privacy, /security, /404 and /careers. No product, how-it-works, integrations, pricing, customer, changelog, blog or docs pages, and no newsletter; social links are X and LinkedIn only.Source

Publish one founder essay every two weeks on a new /writing section, cut into LinkedIn and X posts. Topics: what restaurants and hotels know about regulars that SaaS forgets; the cost of a customer repeating themselves to three teams; what "hospitality at scale" means when agents answer first. Each essay ends with a newsletter sign-up and the early-access link.

Operators follow founders with a clear point of view, and a category is defined by whoever writes about it first and most consistently.

• Essays drift into generic AI talk

  Every essay needs a story from real service work.

• #2 Pick one name for the category and use it on every surface, before the brand hire inherits four

• HiringLapel's description in its job posts: "At Lapel, we believe the most hospitable companies win." It builds "the data, infrastructure, and tools that help customer-facing teams understand every customer"; "Most internet businesses want to treat customers well, but their tools work against them." "We're well-funded, backed by top-tier investors, and already working with exceptional companies," "from fast-growing startups to large enterprises." The team works in person in San Francisco.Source
• HiringHead of Brand & Content (San Francisco, posted June 9, 2026, still listed on lapel.com/careers): "Lapel is building a new category of software, and how the market understands it starts with how we talk about it." The role will "Develop and maintain Lapel's brand voice and positioning across every external surface", "Own the marketing engine across written, video, and launch formats", "Support frequent product launches with structured narratives and polished assets", "Brief and manage freelance writers, designers, and video editors" and "Operate as a close creative partner to the founders".Source
• Your websiteSitemap (checked November 9, 2026): 5 URLs in total: /, /privacy, /security, /404 and /careers. No product, how-it-works, integrations, pricing, customer, changelog, blog or docs pages, and no newsletter; social links are X and LinkedIn only.Source

Add /changelog with one entry per release: what shipped, who it helps (sales, success or support), a short clip or screenshot with fictional data. Bigger entries become launch posts; the monthly roll-up goes to the newsletter and to design partners.

Shipping speed is an early-stage company's best argument against bigger rivals, and a changelog makes it visible and indexable.

• Entries stop after a month

  Make the entry part of the release checklist.

• HiringHead of Brand & Content (San Francisco, posted June 9, 2026, still listed on lapel.com/careers): "Lapel is building a new category of software, and how the market understands it starts with how we talk about it." The role will "Develop and maintain Lapel's brand voice and positioning across every external surface", "Own the marketing engine across written, video, and launch formats", "Support frequent product launches with structured narratives and polished assets", "Brief and manage freelance writers, designers, and video editors" and "Operate as a close creative partner to the founders".Source
• Your websiteSitemap (checked November 9, 2026): 5 URLs in total: /, /privacy, /security, /404 and /careers. No product, how-it-works, integrations, pricing, customer, changelog, blog or docs pages, and no newsletter; social links are X and LinkedIn only.Source

Write one fair page per rival, framed as "with or instead of": what the rival does well, where the account context stops at that team's edge, and how Lapel connects sales, success and support. Include a migration or coexistence guide. Date each page and check claims against the rival's own site.

Comparison searches are high-intent, and a coexistence framing lets Lapel enter accounts that already pay for a team-specific tool.

• Looking small next to big rivals

  Lead with the cross-team view only Lapel offers.

• #6 A "How Lapel works" page built from the primitives the engineers are already building

• Competitor researchRivals' own homepages: Pylon, "The new way to run customer support", "Trusted by 1,800+ B2B customers globally", with support, account and product data available to agents and teams via MCP; Vitally, an AI assistant across customer history, usage and conversations, "Trusted by 600+ Leading Customer Success Teams"; Attio, "Welcome to agentic revenue", "Trusted by 30,000+ customers", with "Universal Context" and 30M MCP tool calls a month; Gainsight, "The Customer Retention Platform", giving "your people and AI agents the context to act at the right moment".See the research Source
• HiringLapel's description in its job posts: "At Lapel, we believe the most hospitable companies win." It builds "the data, infrastructure, and tools that help customer-facing teams understand every customer"; "Most internet businesses want to treat customers well, but their tools work against them." "We're well-funded, backed by top-tier investors, and already working with exceptional companies," "from fast-growing startups to large enterprises." The team works in person in San Francisco.Source

Build an interactive sample account on the homepage: a fictional software customer with a support ticket, a renewal date, a usage drop and a sales thread. The visitor clicks "what Lapel noticed" and "what it did" to see the account view and the coordinated action. No sign-up, no real data; it ends with the early-access link.

Showing beats explaining for a new category, and a hands-on sample filters for buyers who recognise their own mess in it.

• Slows the homepage

  Load it lazily; real visitors pass Core Web Vitals today, so keep it that way.

• #6 A "How Lapel works" page built from the primitives the engineers are already building

• Your websiteHomepage (fetched twice, November 9, 2026): H1 "Setting a new standard for service."; "Lapel builds infrastructure to power every customer interaction on the internet."; promises "hospitality at scale"; says Lapel works with a select group of companies, from startups to enterprises. The buyer buttons "Early access" and "Get in touch" carry no link address in the page HTML, and there is no form, email address or booking link; the page's only links go to /careers, four Ashby job posts, X, LinkedIn and /privacy. No customer logos, testimonials or numbers. Page title "Lapel"; meta description "Interaction operations to support every customer touchpoint."Source
• HiringProduct roles (posted June 9, 2026): a Product Designer for zero-to-one concepts and the design system, a Design Engineer taking interfaces from Figma to production React/TypeScript with attention to performance and accessibility, and a Product Engineer to "Design and implement APIs, services, and integrations". lapel.com/careers also lists a Talent Lead and invites candidates to propose their own role.Source
• PageSpeedHomepage, tested November 9, 2026: mobile performance 74, desktop 75, accessibility 96, SEO 92. SEO flag "Links are not crawlable"; accessibility flag "Links do not have a discernible name". Real visitors pass Core Web Vitals (Chrome UX Report p75: LCP 581 ms, INP 62 ms, CLS 0), so speed is not the problem; lab mobile total blocking time is 1,311 ms.Source

Add a short block to /careers and to the shared job-post boilerplate: "Run a sales, success or support team? Lapel is in early access", linking to /early-access with a careers source tag. Ask candidates in interviews which tools their current team uses and, with permission, whether their team lead would like a look.

Candidate traffic is warm, curious and often from target companies; one line turns it into a measurable buyer source at no cost.

• Candidates feel sold to

  Keep it one quiet line; never pitch in interviews.

• #1 Give buyers a working way in: the homepage links four job posts, but "Early access" has no link address

• Your websiteHomepage (fetched twice, November 9, 2026): H1 "Setting a new standard for service."; "Lapel builds infrastructure to power every customer interaction on the internet."; promises "hospitality at scale"; says Lapel works with a select group of companies, from startups to enterprises. The buyer buttons "Early access" and "Get in touch" carry no link address in the page HTML, and there is no form, email address or booking link; the page's only links go to /careers, four Ashby job posts, X, LinkedIn and /privacy. No customer logos, testimonials or numbers. Page title "Lapel"; meta description "Interaction operations to support every customer touchpoint."Source
• HiringProduct roles (posted June 9, 2026): a Product Designer for zero-to-one concepts and the design system, a Design Engineer taking interfaces from Figma to production React/TypeScript with attention to performance and accessibility, and a Product Engineer to "Design and implement APIs, services, and integrations". lapel.com/careers also lists a Talent Lead and invites candidates to propose their own role.Source

Write a short, specific early-access offer for YC and investor-portfolio companies with growing sales, success or support teams: white-glove setup, a direct line to the founders and a fixed early price. Post it once in the YC community channels and ask each investor for five warm intros to portfolio heads of customer success or support.

Warm intros inside trusted networks convert far faster than cold outreach, and similar-stage startups give quick feedback and quotable results.

• Too many tiny startups

  Set a minimum customer-team size.

• #1 Give buyers a working way in: the homepage links four job posts, but "Early access" has no link address

• Y CombinatorLapel's Y Combinator company page one-liner: "Infrastructure to power every customer interaction."Source
• HiringLapel's description in its job posts: "At Lapel, we believe the most hospitable companies win." It builds "the data, infrastructure, and tools that help customer-facing teams understand every customer"; "Most internet businesses want to treat customers well, but their tools work against them." "We're well-funded, backed by top-tier investors, and already working with exceptional companies," "from fast-growing startups to large enterprises." The team works in person in San Francisco.Source
• Competitor researchRivals' own homepages: Pylon, "The new way to run customer support", "Trusted by 1,800+ B2B customers globally", with support, account and product data available to agents and teams via MCP; Vitally, an AI assistant across customer history, usage and conversations, "Trusted by 600+ Leading Customer Success Teams"; Attio, "Welcome to agentic revenue", "Trusted by 30,000+ customers", with "Universal Context" and 30M MCP tool calls a month; Gainsight, "The Customer Retention Platform", giving "your people and AI agents the context to act at the right moment".See the research Source

Run a monthly dinner for 10-12 heads of support, success and sales operations from San Francisco software companies. Each dinner has one question ("where does your customer repeat themselves?") and a short founder talk, and no product demo unless guests ask. Notes, with permission, become anonymised essays.

Small, well-run dinners build trust with exactly the buyers a new category needs, and they produce research and stories for the content engine.

• Turns into a sales pitch

  No slides; product only on request.

• HiringLapel's description in its job posts: "At Lapel, we believe the most hospitable companies win." It builds "the data, infrastructure, and tools that help customer-facing teams understand every customer"; "Most internet businesses want to treat customers well, but their tools work against them." "We're well-funded, backed by top-tier investors, and already working with exceptional companies," "from fast-growing startups to large enterprises." The team works in person in San Francisco.Source
• Your websiteHomepage (fetched twice, November 9, 2026): H1 "Setting a new standard for service."; "Lapel builds infrastructure to power every customer interaction on the internet."; promises "hospitality at scale"; says Lapel works with a select group of companies, from startups to enterprises. The buyer buttons "Early access" and "Get in touch" carry no link address in the page HTML, and there is no form, email address or booking link; the page's only links go to /careers, four Ashby job posts, X, LinkedIn and /privacy. No customer logos, testimonials or numbers. Page title "Lapel"; meta description "Interaction operations to support every customer touchpoint."Source

Define "first useful view" (for example, one key account with tickets, threads and renewal date joined), measure time to it for every new partner, and remove the slowest steps: connector order, default permissions, a sync progress screen, and a founder check-in when the first view is ready. Target under 24 hours.

Early customers judge a new tool in its first week, and fast time-to-value turns design partners into references.

• Rushing sync quality

  Measure correctness alongside speed.

• HiringThree backend roles (San Francisco, posted May 27, 2026). Primitives: customer records, threads, workflows, permissions and actions, an extensibility model for customers, and primitives usable by people and agents. Core Platform: systems that sync, parse, store, transform, permission and retrieve information from customers' external systems, an integration framework, and workflow infrastructure for long-running jobs and agent-driven actions. Agents: long-horizon agents that remember, retrieve customer context, use tools and take actions, with evals, observability and multi-tenant isolation for enterprise customers.Source
• Your websitePrivacy policy (last updated July 25, 2025): Lapel, Inc. builds software that helps internet businesses "unify customer data and automate operational workflows". Customers connect CRM, support, email or calendar and analytics tools; Lapel processes CRM records, support tickets, product usage data, communication content and recordings of sales or support calls on the customer's behalf. No subprocessor list is published. It may use de-identified or aggregated data for "training and improving models and automated systems".Source

Once a partner has seen value (after idea 15's first useful view), the founder asks for two introductions to peers. Referred teams skip the waitlist and get the same founder onboarding. Thank referrers with early access to new features and credit on the changelog, if they want it.

Priority access costs nothing, matches the exclusive early-access model, and peer introductions close faster.

• Asking too early

  Only ask after a visible win.

• #1 Give buyers a working way in: the homepage links four job posts, but "Early access" has no link address
• #15 Get every new design partner to their first useful account view within one day

• Your websiteHomepage (fetched twice, November 9, 2026): H1 "Setting a new standard for service."; "Lapel builds infrastructure to power every customer interaction on the internet."; promises "hospitality at scale"; says Lapel works with a select group of companies, from startups to enterprises. The buyer buttons "Early access" and "Get in touch" carry no link address in the page HTML, and there is no form, email address or booking link; the page's only links go to /careers, four Ashby job posts, X, LinkedIn and /privacy. No customer logos, testimonials or numbers. Page title "Lapel"; meta description "Interaction operations to support every customer touchpoint."Source
• HiringLapel's description in its job posts: "At Lapel, we believe the most hospitable companies win." It builds "the data, infrastructure, and tools that help customer-facing teams understand every customer"; "Most internet businesses want to treat customers well, but their tools work against them." "We're well-funded, backed by top-tier investors, and already working with exceptional companies," "from fast-growing startups to large enterprises." The team works in person in San Francisco.Source

Generate a monthly one-page digest for each customer's economic buyer: accounts flagged early, actions taken by people and agents, response times, and three short "saves" with outcomes. Teams can edit it before it goes out. With permission, anonymised saves become proof for the homepage (idea 4).

Renewals depend on the buyer seeing value they didn't have to measure themselves, and saves are the most persuasive proof of a hospitality product.

• Overclaiming credit

  Show the signal and the action; let teams judge the outcome.

• HiringThree backend roles (San Francisco, posted May 27, 2026). Primitives: customer records, threads, workflows, permissions and actions, an extensibility model for customers, and primitives usable by people and agents. Core Platform: systems that sync, parse, store, transform, permission and retrieve information from customers' external systems, an integration framework, and workflow infrastructure for long-running jobs and agent-driven actions. Agents: long-horizon agents that remember, retrieve customer context, use tools and take actions, with evals, observability and multi-tenant isolation for enterprise customers.Source
• Your websiteHomepage (fetched twice, November 9, 2026): H1 "Setting a new standard for service."; "Lapel builds infrastructure to power every customer interaction on the internet."; promises "hospitality at scale"; says Lapel works with a select group of companies, from startups to enterprises. The buyer buttons "Early access" and "Get in touch" carry no link address in the page HTML, and there is no form, email address or booking link; the page's only links go to /careers, four Ashby job posts, X, LinkedIn and /privacy. No customer logos, testimonials or numbers. Page title "Lapel"; meta description "Interaction operations to support every customer touchpoint."Source

For the two most-connected tools among design partners, publish a marketplace listing: what Lapel adds to that tool's data, screenshots with fictional data, the trust page and an early-access install path. Link each listing from the integrations page and track installs as a source.

Marketplaces put Lapel in front of admins at the moment they are looking to extend a tool they already pay for.

• Long review times

  Start with the marketplace with the lightest review.

• #5 Publish a trust page for the call recordings and CRM data enterprises will ask about
• #7 An integrations page that names the tools Lapel connects to

• Your websitePrivacy policy (last updated July 25, 2025): Lapel, Inc. builds software that helps internet businesses "unify customer data and automate operational workflows". Customers connect CRM, support, email or calendar and analytics tools; Lapel processes CRM records, support tickets, product usage data, communication content and recordings of sales or support calls on the customer's behalf. No subprocessor list is published. It may use de-identified or aggregated data for "training and improving models and automated systems".Source
• HiringProduct roles (posted June 9, 2026): a Product Designer for zero-to-one concepts and the design system, a Design Engineer taking interfaces from Figma to production React/TypeScript with attention to performance and accessibility, and a Product Engineer to "Design and implement APIs, services, and integrations". lapel.com/careers also lists a Talent Lead and invites candidates to propose their own role.Source

Publish a permissioned, read-first account context API and MCP server: account summary, recent threads, open issues, renewal and usage signals, plus a small set of approved actions. Document it publicly, launch it with two design partners' agents, and price it as a platform add-on. It makes Lapel the account layer that other agents rely on, not just one more app.

Whoever holds the best cross-team account memory becomes infrastructure, which is the company's stated ambition, and API usage makes Lapel hard to replace.

• Agents take wrong actions

  Start read-only; add actions only with approvals and audit logs.

• Distraction from the core app

  Build on the same primitives; no separate data model.

• #5 Publish a trust page for the call recordings and CRM data enterprises will ask about

• HiringThree backend roles (San Francisco, posted May 27, 2026). Primitives: customer records, threads, workflows, permissions and actions, an extensibility model for customers, and primitives usable by people and agents. Core Platform: systems that sync, parse, store, transform, permission and retrieve information from customers' external systems, an integration framework, and workflow infrastructure for long-running jobs and agent-driven actions. Agents: long-horizon agents that remember, retrieve customer context, use tools and take actions, with evals, observability and multi-tenant isolation for enterprise customers.Source
• Competitor researchRivals' own homepages: Pylon, "The new way to run customer support", "Trusted by 1,800+ B2B customers globally", with support, account and product data available to agents and teams via MCP; Vitally, an AI assistant across customer history, usage and conversations, "Trusted by 600+ Leading Customer Success Teams"; Attio, "Welcome to agentic revenue", "Trusted by 30,000+ customers", with "Universal Context" and 30M MCP tool calls a month; Gainsight, "The Customer Retention Platform", giving "your people and AI agents the context to act at the right moment".See the research Source
• Y CombinatorLapel's Y Combinator company page one-liner: "Infrastructure to power every customer interaction."Source

Once onboarding reaches first value within a day (idea 15), publish a simple startup plan (a flat monthly price up to a set number of accounts or seats, with core connectors) and a "talk to us" enterprise tier with the trust page, the context API and custom terms. Startups sign up through early access with a card; founders spend their calls on enterprise deals.

Public pricing filters out poor fits, speeds up small deals and frees founder time for the enterprise accounts that decide the company's trajectory.

• Under-pricing a new category

  Start with a price and raise it for new customers as proof grows.

• Self-serve customers churn without help

  Keep a founder check-in in the first week.

• #15 Get every new design partner to their first useful account view within one day

• Your websiteSitemap (checked November 9, 2026): 5 URLs in total: /, /privacy, /security, /404 and /careers. No product, how-it-works, integrations, pricing, customer, changelog, blog or docs pages, and no newsletter; social links are X and LinkedIn only.Source
• HiringLapel's description in its job posts: "At Lapel, we believe the most hospitable companies win." It builds "the data, infrastructure, and tools that help customer-facing teams understand every customer"; "Most internet businesses want to treat customers well, but their tools work against them." "We're well-funded, backed by top-tier investors, and already working with exceptional companies," "from fast-growing startups to large enterprises." The team works in person in San Francisco.Source
• Competitor researchRivals' own homepages: Pylon, "The new way to run customer support", "Trusted by 1,800+ B2B customers globally", with support, account and product data available to agents and teams via MCP; Vitally, an AI assistant across customer history, usage and conversations, "Trusted by 600+ Leading Customer Success Teams"; Attio, "Welcome to agentic revenue", "Trusted by 30,000+ customers", with "Universal Context" and 30M MCP tool calls a month; Gainsight, "The Customer Retention Platform", giving "your people and AI agents the context to act at the right moment".See the research Source

Each year, mystery-shop 100 well-known software companies as a prospective and existing customer: response time to a sales inquiry, whether support remembers context, whether the same question has to be repeated to a second team, and renewal and cancellation experience. Publish the ranking, the method and the patterns (no private data), with a page per category of software. Invite the top companies to a dinner (idea 14) and offer every company a private breakdown.

Original benchmarks earn press, links and AI citations, put Lapel's language in buyers' mouths, and give sales a reason to contact every company on the list.

• Companies dislike being ranked

  Publish the top performers and patterns; share low scores only privately.

• #8 A founder essay series on "the most hospitable companies win", published on lapel.com and LinkedIn

• HiringLapel's description in its job posts: "At Lapel, we believe the most hospitable companies win." It builds "the data, infrastructure, and tools that help customer-facing teams understand every customer"; "Most internet businesses want to treat customers well, but their tools work against them." "We're well-funded, backed by top-tier investors, and already working with exceptional companies," "from fast-growing startups to large enterprises." The team works in person in San Francisco.Source
• HiringHead of Brand & Content (San Francisco, posted June 9, 2026, still listed on lapel.com/careers): "Lapel is building a new category of software, and how the market understands it starts with how we talk about it." The role will "Develop and maintain Lapel's brand voice and positioning across every external surface", "Own the marketing engine across written, video, and launch formats", "Support frequent product launches with structured narratives and polished assets", "Brief and manage freelance writers, designers, and video editors" and "Operate as a close creative partner to the founders".Source

Pull the list of URLs other sites link to (from Search Console's Links report and a backlink tool), plus old paths from the Archive's URL index. Redirect the ones that get links or traffic to the closest current page (homepage, /how-it-works, /writing) with 301s in Framer. Leave unrelated or spammy paths as 404s.

Redirecting lost links is one of the cheapest search wins there is, and an old domain often has more of them than a new company expects.

• Old links come from irrelevant or low-quality sites

  Redirect only relevant, reputable links.

• #6 A "How Lapel works" page built from the primitives the engineers are already building

• Site historyDomain history: lapel.com was registered in 1996 and first archived in 1998; the Internet Archive holds 203 snapshots over 26 active years, the busiest in 2018, long before today's five-page site.Source
• Your websiteSitemap (checked November 9, 2026): 5 URLs in total: /, /privacy, /security, /404 and /careers. No product, how-it-works, integrations, pricing, customer, changelog, blog or docs pages, and no newsletter; social links are X and LinkedIn only.Source
• Search resultsA web search for "lapel" (November 9, 2026) returns only suit and tailoring pages, led by Wikipedia's "Lapel" article, in the top 25 results; lapel.com does not appear.Source

Ship a library of ten service-standard templates as ready-made workflows: "never make a customer repeat themselves" (context handed over between support and success), "recover within a day" (follow-up after a bad ticket), "remember the regulars" (top-account changes flagged to the owner), "close the loop" (feature-request status sent back to the requester). Each template has a one-page explanation that doubles as public content.

Templates speed up activation, make the hospitality story concrete, and give the brand a library of ideas no rival has.

• Templates feel generic

  Build each from a real partner's practice.

• #15 Get every new design partner to their first useful account view within one day

• HiringLapel's description in its job posts: "At Lapel, we believe the most hospitable companies win." It builds "the data, infrastructure, and tools that help customer-facing teams understand every customer"; "Most internet businesses want to treat customers well, but their tools work against them." "We're well-funded, backed by top-tier investors, and already working with exceptional companies," "from fast-growing startups to large enterprises." The team works in person in San Francisco.Source
• HiringThree backend roles (San Francisco, posted May 27, 2026). Primitives: customer records, threads, workflows, permissions and actions, an extensibility model for customers, and primitives usable by people and agents. Core Platform: systems that sync, parse, store, transform, permission and retrieve information from customers' external systems, an integration framework, and workflow infrastructure for long-running jobs and agent-driven actions. Agents: long-horizon agents that remember, retrieve customer context, use tools and take actions, with evals, observability and multi-tenant isolation for enterprise customers.Source
• Your websiteHomepage (fetched twice, November 9, 2026): H1 "Setting a new standard for service."; "Lapel builds infrastructure to power every customer interaction on the internet."; promises "hospitality at scale"; says Lapel works with a select group of companies, from startups to enterprises. The buyer buttons "Early access" and "Get in touch" carry no link address in the page HTML, and there is no form, email address or booking link; the page's only links go to /careers, four Ashby job posts, X, LinkedIn and /privacy. No customer logos, testimonials or numbers. Page title "Lapel"; meta description "Interaction operations to support every customer touchpoint."Source