This is the copy the lessons used. Work done against it still stands. The current notes are at /lotssocial.
This is the real thing, not a version made for you. These are the notes Scout, Herald, Ranker and the rest actually read before they write anything. Nothing has been simplified.
Three rules for using it:
1. Note 8 first. It lists what marketing may not claim — no testimonials, no customer counts, no "trusted by", no case studies, because we have none. Breaking that list is the most expensive mistake available here.
2. Never quote a price from memory. Note 6 explains the model; the live figures are at lots.social/pricing.md. Fetch it.
3. It goes stale. Note 5 was wrong about competitors until yesterday. If something here contradicts what you find, tell me — that is worth more to me than the note.
Until now I withheld this deliberately so I could compare your research against ours. That comparison is done and it was useful — it showed exactly where people invent facts when they have none. Now withholding it just produces wrong work, so here it is.
1. Product Overview & Capabilities
Checklist note 1 of 9. Before publishing anything, read note 8 (Business Constraints) — it lists what marketing may not claim.
What it is
LotsSocial is a social media management platform for 12 networks that you can run three ways: from the web app, from an AI agent built into it, or from the AI client you already use, over a hosted MCP server and REST API.
Built by LotsTech AI Solutions Private Limited, India (D-U-N-S 772073652), by a single founder-developer, Sivaguru Ayyadurai. It is one of several LotsTech products sharing one login and one credit balance: LotsAgent (AI agents), LotsBlog (blog & SEO), LotsLink (short links & QR), LotsCommerce (store & orders), LotsTeam (founder tooling).
The problem it solves
Writing a post is not the slow part. The slow part is everything after: reformatting per network, hunting for the photo across a phone and a laptop, pasting into each app. And if you use ChatGPT for the writing, you re-explain your business every session — because it does not remember you, hold your accounts, or keep a calendar.
How it works
- Connect accounts once — OAuth, no passwords stored, about two minutes.
- Describe the business once — what you sell, who buys, how you talk. Saved as brand context.
- Ask in plain language — one instruction produces a separate draft per network, written for that network.
- Approve — nothing publishes without you. Edit anything first.
- It schedules and publishes, with retries when a network fails.
Core value proposition
Run social media your way — from the app, our agent, or your own AI. Say what you want; it writes per platform from your saved business context and waits for your approval. Billed on connected accounts and storage, never per seat.
The 12 networks
LinkedIn · Instagram · X · Google Business · Facebook · YouTube · Reddit · Threads · TikTok · Pinterest · Bluesky · Mastodon
Exactly twelve. No plan changes the list. Never write "12+".
Features → benefits
| Capability | What it means to the customer |
|---|---|
| Brand context saved once | "It knows my business" — drafts stop sounding generic, and you stop retyping |
| Per-platform drafting | One ask, twelve destinations, each written for that place |
| Approval gate on every path | "Nothing goes out unless I say so" — the answer to AI fear |
| Independent review of AI posts | An AI-written post is rejected unless its review is current and passing |
| Calendar + bulk scheduling | Set up a month in one sitting, per brand or across all of them |
| Media library | Photos and video in one place, resized per platform on the way out |
| Comments inbox | Reply across every account without opening every app |
| Campaigns | A goal, the posts that served it, results attributed back even when engagement lands late, plus a dated retrospective |
| Analytics | Per post and aggregated per account |
| Unlimited workspaces & brands | A workspace per client, separated rather than tagged |
| Unlimited team members | Adding a teammate never changes your bill |
| MCP server + REST API | Your own Claude/ChatGPT/Cursor can draft, schedule and publish |
| Voice, email, Telegram | Dictate in the app, email lots-social@lotsagent.com, or message @LotsSocialBot |
The three surfaces
The app, the built-in agent, and your own AI all sit on the same accounts, the same brand context and the same approval rules.
Corrected 15 September 2026. This section used to call the third surface our differentiator and say no competitor offered it. That is no longer true — Buffer offers MCP on every plan including free, and Hootsuite shipped connectors in June 2026. See note 5.
Claim the three surfaces as a real capability, not as something only we have. The differentiator now has to come from the commercial model — per connected account rather than per seat, unlimited team members and brands, publishing API on every plan, usable on credits alone — and each of those needs checking against a live competitor pricing page before it is published.
What it deliberately does not do
No autonomous posting mode · no paid ads or ad-budget management · no influencer outreach · no networks beyond the 12 · no white-label client portal or custom client domain · no per-seat billing (so no seat count to compare on) · no self-serve tier above Agency.
Proof points available today
Pre-launch, so the proof is the product and the mechanism, not results:
- The product is live and complete at lots.social — screenshots, real UI, a ~2-minute demo video
- A live MCP server anyone can point a client at, and a published OpenAPI 3.0 spec — proof by inspection
- A verifiable pricing model a reader can check against any competitor's own pricing page
- 14-day money-back guarantee for first-time subscribers
- The founder is reachable and answers directly
We have no testimonials, logos, customer counts, case studies or ratings. See note 8 — inventing them is the single worst failure mode available here.
Links and assets
All URLs, image assets, naming rules and brand colours live in note 7 (Brand Assets & Canonical Links). They are kept there so there is exactly one place to update when a page moves — six pages were removed on 8 Sep 2026 and note 7 records which. Never link to a page without checking it there first.
When this note is not enough
Fetch https://lots.social/llms-full.txt. It is the whole site as flat text, and its prices are read live from the billing catalogue at request time. If it contradicts this note, it wins.
2. Target Customer & ICP
Checklist note 2 of 9.
Three distinct ICPs with pains that do not overlap, which is why the site is a router: the homepage sends you to your own page rather than arguing all three cases at once. Each has its own landing page and its own markdown mirror.
ICP 1 — Business owners (SMB and solo operators)
lots.social/business · business.md
Who: the person who owns the business and posts for it. Dental clinic, café, salon, boutique, gym, physio practice, photographer, solo consultant, small D2C shop. 1–20 staff. No marketing team, no agency, no marketing budget line. They are an operator, not a marketer.
Situation: they know social matters and resent how long it takes. If they have tried ChatGPT they hit a second wall — it forgets the business every session and still cannot post.
Great-fit traits: 3–6 accounts to run · posts for themselves · has a phone full of photos · has abandoned a social schedule at least once · nervous about AI tone.
Their words (use theirs, not ours):
| We say | They say |
|---|---|
| Brand context | "It knows my business" |
| Media library | "My photos in one place, not hunting through my phone" |
| Per-platform drafting | "It writes it right for each one" |
| Bulk scheduling | "Set up the whole month in one sitting" |
| Approval workflow | "Nothing goes out unless I say so" |
| Unified inbox | "Reply to comments without opening every app" |
| Analytics | "What actually worked" |
| Workspaces / brands | (never use these words with them) |
Never put MCP, API, OAuth, webhook, endpoint or workspace in copy aimed at this segment.
Emotional drivers: guilt (haven't posted in three weeks) · embarrassment (competitor's feed looks professional) · fear of AI saying something tone-deaf under their name · time.
Plan fit: Starter ($12) or Plus ($24). Do not show them the Agency plan — a $99 tier makes a $12 product look like a compromise.
ICP 2 — Agencies and freelance social managers
lots.social/agencies · agencies.md
Who: boutique agencies (2–15 people), content studios, freelance social managers running accounts for other businesses. Typically 5–30 clients. Commercially the strongest segment — highest account count, highest retention, and they tell each other what they use.
Situation: the roster grows costs before it grows margin. Per-seat, per-workspace and per-brand billing means the tenth client costs more to service than the third.
Great-fit traits: 6+ clients · has hired or is about to · currently on a per-seat tool · builds client reports by hand · cares about margin per retainer.
Their words: roster · book of clients · retainer · scope · deliverables · client sign-off · reporting · margin · utilisation. They know social tools — skip the basics and talk peer to peer.
Plan fit: Pro ($49) for a freelancer with 5–10 clients; Agency ($99) for a real roster.
ICP 3 — Builders, developers and AI agent users
lots.social/api · api.md
Who: technical founders, indie hackers, solo developers, and anyone building with AI agents. Two shapes: the builder who needs social publishing inside their own product, and the agent user who wants their daily-driver AI to be able to post, not just draft.
Situation: they already live in Claude, ChatGPT, Cursor, Gemini or an MCP client. Evaluation is: does it exist, does it authenticate cleanly, what does it cost, can I try it now — in under a minute, with no sales call.
Great-fit traits: already uses an MCP client · wants no subscription · will read an OpenAPI spec · building on top of us for their own users.
Their words: MCP · OAuth 2.1 · PKCE · REST · OpenAPI · Bearer token · self-serve · no lock-in. Write plainly and technically. High tolerance for detail, very low tolerance for adverbs.
Plan fit: frequently no plan at all — credits only. When they subscribe it is usually Starter or Plus.
Who is NOT a good fit
Be willing to say so — chasing these costs more than it earns:
- Enterprises and large marketing teams. No SSO, no enterprise tier, no procurement process, no dedicated support. There is deliberately no tier above Agency.
- Anyone who wants a white-label client portal or custom client domain. It does not exist.
- Anyone wanting fully autonomous posting. The approval gate is not configurable away. If "set it and forget it" is the requirement, we are the wrong product.
- Paid-social / performance marketers. No ads, no budgets, no creative testing.
- Influencer-marketing agencies. No outreach or campaign-management tooling for that.
- Anyone whose networks aren't in our 12 — notably Snapchat, WhatsApp Business, Discord, Telegram channels, Xiaohongshu, WeChat, Weibo.
- Very large single-brand teams with heavy multi-stage editorial workflows and role permissions beyond what we offer.
- Price-only shoppers. Publer and free tiers exist; we win on model and capability, not on being cheapest.
Segment weighting
Agencies are the highest commercial value per customer. Business owners are the largest addressable group and the hardest to reach. Developers are the cheapest to serve and the most likely to arrive because an AI recommended us. All three are real — none is a side bet.
Note: everything above about how customers speak and what they feel is hypothesis, not research — see note 9.
3. Problems, Use Cases & Objections
Checklist note 3 of 9. Every answer below is checkable. If an objection is not covered here, check https://lots.social/llms-full.txt or ask — do not improvise.
Where the problem statements come from: this note describes the problem as I see it from running my own accounts. The sequence is observed. It is not measured. Use the shape of it, do not quote figures from it.
The problems, per segment
Business owners
Writing the post is the quick part and is fine. Then: crop for Instagram, shorten for X, make it sound professional for LinkedIn, find the photo (phone? laptop? WhatsApp?), open each app in turn, paste, adjust. Most of the time goes there, not on the writing. Next week they don't bother. If they use ChatGPT they re-explain the business every session and still can't post from it.
Agencies and freelancers
State this correctly: winning clients is hard. That is a different problem and conflating them insults the reader. The problem here is that the roster raises costs before it raises margin — per seat, per workspace, per client brand. The tenth client costs more to service than the third, and the extra cost is not the work. Plus: fifteen client voices, fifteen approval chains, and a client asking "what did you post last month and did it do anything?" that takes an hour to answer.
Builders
They want social publishing in their product or their agent, and every option is either a subscription wall, an enterprise sales gate, or a scraper. Docs that lag the API. No clean way to let an agent post safely on a user's behalf.
Triggers — when they start looking
| Segment | Trigger |
|---|---|
| Business owner | Opening a second location · seasonal push (festival, holiday, new term) · competitor's feed visibly improving · Google Business listing going stale · firing an agency that cost too much · new website launch |
| Agency | Signing client 6, 10 or 15 · a seat-based renewal quote arriving · hiring a junior and discovering they cost a seat · losing a client and the tool bill not dropping · a client asking for reporting the current tool can't produce |
| Builder | Starting a project that needs to publish · adopting an MCP client · hitting an API paywall elsewhere · wanting their agent to actually do things, not just draft |
Major use cases
- The weekly ask — "draft this week for the spring booking push", approve, done.
- Load a month in one sitting — bulk scheduling with retries, per brand or across a whole book of clients.
- A campaign with a goal — goal and timeframe set, posts written toward it, results attributed back even when engagement lands late, dated retrospective at close.
- Client-safe delivery — draft, send to client for sign-off, publish on approval; client authorises their own accounts by link.
- Publish from your own AI — point Claude/ChatGPT/Cursor at the MCP server; it drafts, schedules and publishes through the same approval rules.
- Reply without app-hopping — one comments inbox across every connected account.
- Reuse media properly — upload once, resized per platform on the way out.
Desired outcomes
Show up consistently without it eating an evening · sound like themselves, not like AI · never be embarrassed by something that went out · (agency) keep client ten as profitable as client three · (agency) walk into a renewal with the numbers already assembled · (builder) ship social publishing in an afternoon without a sales call.
How they solve it today
- Manually — posting natively in each app. Free, and the reason most small businesses go quiet.
- A scheduler (Buffer, Hootsuite, Later, Publer) — solves distribution, leaves the writing and the context to you.
- ChatGPT / Claude — solves the writing, forgets the business, holds no accounts, keeps no calendar.
- Chat + scheduler, by hand — the most common real workflow, and the copy-paste tax we attack.
- An agency or freelancer — expensive; often what the SMB is leaving.
- Zapier / Make / n8n — the builder's DIY route. Moves data, holds no brand context, no review or approval, and they maintain it.
Objections and answers
Trust and AI fear
"Will it post something embarrassing under my name?"
No. Nothing publishes without your approval, on every path — app, built-in agent, API and MCP server. There is no autonomous mode to leave switched on by accident. An AI-written post is additionally rejected unless its independent review is current and passing.
"Won't AI posts sound generic?"
They sound generic when written from a prompt. LotsSocial writes from your saved business context — what you sell, who buys it, how you talk — and you edit anything before it goes out.
"Do you store my passwords?"
No. Accounts connect by OAuth. Setup is about two minutes.
The ChatGPT question — the most common one
"I already use ChatGPT for this."
It writes well; that is not the gap. What it does not do on its own is remember your business between chats, hold your accounts, keep a calendar, or publish on a schedule. And if you'd rather keep working in ChatGPT, you can — our MCP server lets it publish through the same accounts, context and approval rules.
Never say ChatGPT cannot publish to social accounts. It can, through us. That claim has had to be corrected twice.
Price and commitment
"Another subscription."
A subscription is one way to pay, not a requirement. Credits alone fund everything and purchased credits never expire. There's also a 7-day free trial on every paid plan and 1,500 free credits on signup — no card.
"It's more expensive than [X]."
Compare the model, not the sticker. We bill on connected accounts and storage; workspaces, brands, team members and posts are unlimited. Most tools charge for the second, third and fourth of those. For an agency the seat line alone usually closes the gap.
"What if it's not for me?"
14-day money-back guarantee for first-time subscribers. Cancel any time, no fees; the plan runs to the end of the period.
Agency-specific
"Is this a single-user toy?" — Workspace per client with its own brand context, approvals and accounts. Unlimited team members. Clients authorise their own accounts by link, so nobody hands over a password.
"Can I white-label it?" — No. No rebranded client portal, no custom client domain. Say it plainly; do not fudge it.
"Migrating 15 clients sounds painful." — Clients authorise their own accounts by link; brand context is one pass per client. Real work, but hours not weeks.
Developer-specific
"Do I need a subscription for the API?" — No. Credits alone fund everything; a credits-only customer has no subscription at all.
"Will your docs be out of date?" — They're generated from the live tool registry, and every capability is served as an MCP tool and a REST endpoint from that one definition, so the two cannot drift.
"Can my agent post autonomously?" — No, deliberately. Same validation and approval path as the dashboard. For anyone building on top of us that's a guarantee about their own users' accounts.
Company
"Who's behind this? Will you be around?" — LotsTech AI Solutions Private Limited, built by a solo founder-developer. Be straight about it: for agencies and developers, direct access to the person who built it is an argument in our favour.
"Do you have customers?" — We are new. Do not invent an answer. Say we're early, point at the product, the trial and the free credits, invite them to try it. See note 8.
When the honest answer is no
Say no, offer what we do have, move on. A conceded limitation makes every other claim more believable — a fudged one gets found out exactly when someone was about to pay.
Note: these problems and objections are anticipated, not collected from customers — see note 9.
4. Positioning, Messaging & Voice
Checklist note 4 of 9.
Category
Social media management platform. Not "AI writing tool", not "content generator", not "automation platform". The buyer is searching for a scheduler; we win by being a complete one plus something the others cannot do. Claim the category, then take the extra ground. Never position as an alternative to having a scheduler.
Positioning statement
For business owners, agencies and builders who already know they should be posting, LotsSocial is a social media management platform you can run from the app, from a built-in AI agent, or from the AI you already use. Unlike Buffer, Hootsuite, Later and Publer, it holds your brand context and your accounts behind all three — so asking for a post and having it go out are the same action — and it bills on connected accounts and storage, never per seat.
Elevator pitch (30 seconds)
Most social tools give you a queue: you write the posts, they publish them on schedule. LotsSocial saves your business context once — what you sell, who buys it, how you talk — and writes from it. Say "draft this week for the spring push" and you get a separate post for each of twelve networks, written for that network, waiting for your approval. You can do that in the app, by talking to the agent inside it, or from your own ChatGPT or Claude. And you're billed on connected accounts and storage — teammates, brands and workspaces are unlimited.
The main promise
Run social media your way.
Every landing page H1 is a variation. Stay inside this family, and keep the verb "Run" — it carries ownership and control, which is the emotional core. These buyers don't want the work taken away from them; they want it to stop being tedious.
| Page | Headline |
|---|---|
| Home | Run social media your way — from the app, our agent, or your own AI. |
| /business | Run your social media by talking to it. |
| /agencies | Run every client's social media. Pay per account, not per client. |
| /api | Run your social media from your own agent. |
Message hierarchy
Use in order. If you get one line, use level 1.
- Run social media your way — from the app, our agent, or your own AI. (the three surfaces — claim the capability, never that we are the only ones. See note 5, corrected 21 Sep.)
- Say what you want; it writes per platform and waits for your approval.
- Your business explained once, reused forever. (why the drafts are good, and why AI chat can't match it)
- Pay for accounts and storage, not seats. (a differentiator, not a discount)
- Twelve networks. (table stakes — it belongs last)
The most common mistake is leading with 5. "Connect 12 networks" was the site's own meta description for months and was replaced for exactly this reason: a count is not a reason anyone came.
Key differentiators
- Three surfaces, one account — app, built-in agent, your own AI over MCP/REST, sharing accounts, context and approvals.
- Saved brand context reused across all three surfaces. Others store brand context; what is ours is that one object serves app, agent and API. Describe the shape, never claim exclusivity.
- Hosted MCP server. Buffer and Hootsuite have one too. Claim it as a capability, not as a first.
- Billed on accounts and storage; unlimited seats, brands, workspaces, posts.
- Usable with no subscription at all — credits only.
- Approval-first everywhere, including the API. A trust asset, not a limitation.
Positioning against general AI chat
ChatGPT and Claude write good social posts. Say so. The earlier version of this argument claimed they couldn't reach your accounts, which is false and had to be corrected twice. The real difference is what happens after the words exist: no memory of your business between chats, no accounts, no calendar, no schedule.
Then the disarming move: if you'd rather stay in ChatGPT, you can — the MCP server lets it publish through the same accounts, context and approval rules. This turns a competitor into a distribution channel.
What we are not
Not an autopilot — never sell "set it and forget it" · not the cheapest, so sell the billing model · not an enterprise platform · not a Buffer clone with AI bolted on. The comparison we want is "everything they do, plus the part they leave to you".
Voice and style
The voice in one line
Plain, specific, and slightly understated. Describe what the product does and let that be impressive. Don't tell the reader how to feel about it.
Five rules
- Say the thing, then stop. No wind-up.
- Concrete beats abstract. "Hunting for the photo across a phone and a laptop" beats "streamlined asset management".
- Own the limits. Admitting a boundary is the cheapest credibility available and makes the claims beside it believable.
- Their words, not ours. See note 2 for each segment's vocabulary.
- Short sentences carry the point. Under fifteen words when it matters.
Words we use
say · ask · approve · publish · draft · connect · run · post · account · brand · client · calendar · month · evening
Words we avoid
leverage · utilise · seamless · robust · cutting-edge · game-changing · revolutionary · unlock · supercharge · effortless · elevate · solutions · offerings · empower · enable · 10x · hack · ninja · rockstar · "In today's digital landscape" · "AI-powered" as the main claim (everyone's is — say what the AI does) · exclamation marks · emoji in body copy or email subject lines (fine on social, where the platform expects them).
Headline pattern that works here
A two-part statement where the second part turns the first:
- "The tenth client costs more than the third. / And it isn't the work."
- "Everything a scheduler does. / Plus the part they leave to you."
- "Show what the work did. / Before the renewal call."
- "Writing the post is the easy part. / Everything after it isn't."
Tone by segment
- Business owners — warm, plain, zero jargon. Their evening, their phone, their competitor's feed. Never make them feel behind.
- Agencies — peer to peer. Respect the expertise, talk margin and roster, skip the basics.
- Developers — terse and technical. URL first, adjective never.
Mechanics
British-leaning spelling, consistent within a piece · em dashes with spaces — like this — sparingly · sentence case for headlines and buttons, not Title Case · numerals for 10+, words below ("twelve networks" in prose, "12 networks" in a badge or table) · prices $12/month, USD unless stated · no Oxford comma unless it removes ambiguity.
Naming, colours and image assets
In note 7 (Brand Assets & Canonical Links) — product and company capitalisation, brand colours, logo and share-card files with their required dimensions, and what is retired. Kept in one place so a rename or a new asset is a single edit.
The test
Read it aloud. If it sounds like a person explaining their product to someone at the next table, it's right. If it sounds like a press release, cut the first sentence and try again.
5. Competitive Landscape
Checklist note 5 of 9. Last reviewed 21 September 2026.
Competitor pricing moves. Re-check their public pricing page before publishing any number about them, and link to it. A wrong comparison is a false claim about someone else — worse than one about ourselves.
The comparison on the site
lots.social/#compare sets us against Buffer, Hootsuite, Later, Publer:
| Us | Them | |
|---|---|---|
| 12 networks | yes | all yes |
| Calendar, bulk scheduling, media library | yes | all yes |
| Analytics and reporting | yes | all yes |
| Billed by connected account, not seat | yes (accounts + storage) | mixed — Hootsuite per seat |
| Unlimited team members on every plan | yes | none |
| Unlimited brands and workspaces | yes | all capped by plan |
| An AI agent you can brief, not a caption button | yes | all "caption assist" |
| Saved brand context reused by app, agent and API | yes | removed from the site table 21 Sep — see below |
| Hosted MCP server for your own agent | yes | Buffer yes (all plans, incl. free) · Hootsuite yes (connectors, Jun 2026) · Later no · Publer no |
| Publishing API on every plan | yes | none / enterprise / higher tier |
| Usable with no subscription at all | yes (credits) | none, except one free tier |
The strategic point: rows 1–3 are parity and must be claimed loudly — a differentiated product loses to an ordinary one when the buyer can't confirm the ordinary things exist.
Corrected 15 September 2026. This note previously said no competitor had an MCP server, and the site's comparison table published it. That was wrong: Buffer has offered MCP on every plan including free, and Hootsuite shipped MCP connectors on 24 June 2026. The row is fixed on the site.
So MCP access is no longer a differentiator — it is becoming parity, and should now be claimed the way rows 1–3 are: loudly, as a thing that exists, not as a thing only we have.
What still looks defensible — and every one of these is a pricing-page claim a reader can check, so re-verify before publishing:
- Billed by connected account, never per seat (Hootsuite is per seat — the clearest wedge)
- Unlimited team members, brands and workspaces on every plan
- Publishing API on every plan rather than enterprise or higher tier
- Usable with credits and no subscription at all
Corrected 21 September 2026 — the saved-brand-context row. It was crossed for all four rivals and that was never verified. Checked: Postplanify sells "AI Training & Knowledge Base" and "Brand Voice" alongside API and MCP access. Vista Social sells "AI Training & Knowledge" with MCP. FastSocial has a brand profile step storing business name, industry, audience, voice and topics — reused across its own content generation, with no evidence it reaches an API or external agent.
The row is removed from the site table. The capability is not ours alone.
What survives is shape, not scarcity: here the context is one stored object that the app, the built-in agent and your own AI over MCP all read. Elsewhere it is a per-surface setting. That is a real difference and it belongs in prose where it can be explained — not in a cell with four crosses that has to keep being right.
Found independently by Scout and by Nandhini (intern, batch 1) on the same day.
Battlecards
Buffer
- Strength: simple, well-liked, cheap entry, strong brand.
- We win on: brands and channels capped per plan · AI is caption assistance, not an agent you brief · no publishing API on ordinary plans · no per-account billing.
- Do not claim: that Buffer has no MCP server — it does, on every plan including free (
buffer.com/mcp). And treat "no saved brand context across surfaces" as unverified. - Line: "Buffer queues what you write. LotsSocial writes it from your business, then queues it."
Hootsuite
- Strength: enterprise credibility, breadth, long incumbency.
- We win on: per-seat billing — this is the wedge. A growing agency pays for every person. Expensive at the low end, heavy UI.
- Line: "Every teammate you add costs money there. Here they don't."
- Target: agencies and freelancers holding a renewal quote.
Later
- Strength: Instagram-first, visual planning, popular with creators.
- We win on: channel bundles rather than a clean account model · team seats capped by plan · no agent, no API for most, no MCP.
- Line: "Later plans the grid. LotsSocial runs the whole account."
Publer
- Strength: genuinely good value, per-account pricing (closest model to ours), has a free tier.
- We win on: the agent, saved brand context, MCP and API, unlimited team members.
- Do not fight on price. Their free tier means "we're cheaper" will not land. Say "we do more with the same billing model".
- Line: "Similar billing. The difference is what happens before the post exists."
ChatGPT / Claude / general AI chat
Not really a competitor — the status quo for the business-owner segment.
- Never claim they cannot publish to your accounts. They can, through our MCP server. Corrected twice already.
- We win on: no memory of your business between chats, no accounts, no calendar, no schedule.
- The disarming move: "If you'd rather stay in ChatGPT, you can — it can publish through LotsSocial." Converts a competitor into a distribution channel and is one of our strongest arguments.
Sprout Social, Sendible, Metricool, Loomly, SocialBee
Not on the site's table. Same shapes: Sprout is enterprise, per-seat and expensive; Sendible and Loomly are agency-oriented with capped brands; Metricool and SocialBee are value plays. If you need to compare, pull their live pricing page and use the rows above.
Zapier / Make / n8n
The builder's DIY alternative. They move data but hold no brand context, do no review or approval, and the user builds and maintains the flow. Acknowledge; don't attack.
Doing nothing / posting natively
The real default for most small businesses, and the biggest competitor by volume. Free, and the reason feeds go quiet. Beat it on the work after the writing, not on features.
Where we are genuinely different
- Three surfaces on one account (app / built-in agent / your own AI).
- Saved brand context reused across all three surfaces. Not "nobody else has this" — saved brand context exists elsewhere (Postplanify, Vista Social, FastSocial). What is ours is the shape: one stored object the app, the agent and the API all read, rather than a per-surface training blob.
- A hosted MCP server. Not exclusive — Buffer has one on every plan including free, Hootsuite since June 2026.
- Billing on accounts and storage with unlimited seats, brands and workspaces.
- Usable with no subscription at all.
Where they beat us — know this, don't hide it
Brand recognition and trust (we have none yet) · established review presence on G2/Capterra · white-label for agencies (Sendible, others) · free tiers (Publer) · enterprise features, SSO and procurement (Hootsuite, Sprout) · Instagram-specific visual planning depth (Later) · a support team rather than one founder.
Rules for comparative content
- Compare only on facts visible on their own public pricing or docs page, and link to it.
- Never characterise their product quality or their team. Compare models, not merit.
- Re-verify before publishing.
- Comparison pages ("LotsSocial vs Buffer") are high-intent SEO and worth building — but they must be genuinely useful, including where the competitor is the better choice. A comparison that never concedes anything reads as an ad and converts like one.
6. Pricing & Commercial Model
Checklist note 6 of 9.
Never quote a price from memory. Prices live in a central billing catalogue. The live, always-correct copy is https://lots.social/pricing.md — fetch it before publishing any number. The figures below were verified 4 September 2026 and are here so you understand the model.
The model in one sentence
Billed on connected social accounts and media storage, charged daily on what you actually hold. Nothing else.
Unlimited on every plan, at no cost: workspaces, brands, team members, posts. No per-seat, per-client or per-brand charge.
Sell the model, not the number. We are not the cheapest and should never try to be.
Plans (4 Sep 2026)
| Plan | Monthly | Annual | Lifetime | Accounts | Storage | Credits/mo |
|---|---|---|---|---|---|---|
| Starter | $12 | $120 | $349 | 5 | 5 GB | 3,500 |
| Plus | $24 | $240 | $599 | 15 | 15 GB | 7,500 |
| Pro | $49 | $490 | $1,299 | 35 | 50 GB | 16,000 |
| Agency | $99 | $990 | $2,499 | 100 | 150 GB | 40,000 |
- Annual = ten months' price for twelve — two months free.
- Lifetime is one payment with a one-off credit grant instead of a monthly one.
- No tier above Agency, deliberately. A bigger roster adds credits, not an enterprise contract. Never invent "Enterprise — contact us".
Credits
- Connected accounts: 1,000 credits per account per month
- Media storage: 300 credits per GB per month
- Purchase rate: 1,000 credits per USD (15 per INR), minimum $10
- Unused plan credits roll over up to 3× the monthly grant while subscribed; forfeited 60 days after cancelling
- Purchased credits never expire
- A short AI job ≈ 42 credits; a long tool-using job ≈ 237
Credits are LotsTech Credits — one balance across every Lots product. A genuine reason to prefer the group.
Paying without a plan
A subscription is not required. Buy credits, enable credit billing, connect only what you need. A credits-only customer has no subscription row at all — which matters when counting customers (see note 8). This is the default path for developers.
Free trial and starter credits — say this positively
- 7-day free trial on every paid plan, monthly and annual
- 1,500 free credits for every new account, valid 30 days
- No card required
"Free to start", "start free", "try free", "no card required" are all correct and encouraged.
There is no free plan — a $0 tier you stay on. It was retired before launch and never had a user, so do not lead with its absence. Copy that opens "There is no free plan" leads with what we withhold. Say what someone gets.
Refunds and cancellation
- 14-day money-back guarantee for first-time subscribers to a paid plan; request within 14 days of initial billing.
- Beyond 14 days refunds are generally not provided, though exceptions are considered.
- Cancel any time, no fees. The plan runs to the end of the billing period.
- After cancellation, data is preserved 30 days for reactivation, then permanently deleted.
- Full terms:
lots.social/refund-policy.
Two mistakes to avoid
- Do not derive a per-account price across plans. The plan price buys accounts and storage and credits together, so dividing by accounts alone overstates the account cost — and because small plans carry proportionally more credits, a per-account table makes Starter look like the expensive one. The one allowed exception: "Agency works out under $1 per connected account", as a single headline claim.
- Do not invent a tier, add-on, discount or network. No student/nonprofit/annual-only discounts exist unless the catalogue says so.
What drives upgrades and expansion
- Connecting more accounts — the primary and intended expansion path. An agency signing clients climbs Starter → Plus → Pro → Agency naturally.
- Media storage — video-heavy users hit GB before accounts.
- Credit consumption — heavier AI use, more brands, more research.
- Annual — two months free is the argument.
- Lifetime — for someone who has decided, and who dislikes subscriptions. Attractive to the developer segment.
- Cross-product — credits work in LotsAgent, LotsBlog, LotsLink, LotsCommerce. Someone already paying for one has a reason to try another.
How to talk about price by segment
- Business owners — "From $12 a month. Free to start, no card." Show Starter and Plus only.
- Agencies — lead with the model (unlimited clients, seats and brands; billed on accounts and storage), then "$99 for 100 accounts, under $1 each".
- Developers — lead with "no subscription required". Credits and the daily account rate. Price is rarely their blocker; the subscription wall is.
Currency
Prices are USD. Credits can also be purchased in INR.
7. Brand Assets & Canonical Links
Checklist note 7 of 9. Every URL below was checked live on 8 September 2026.
Never invent a URL. If a page you want does not exist, say so rather than linking to a 404 or a redirect. Six pages that existed on 4 September were removed on 8 September — see "Retired" below.
Marketing pages — the live surface
| Page | URL | For |
|---|---|---|
| Home | https://lots.social | Router for all three segments |
| For businesses | https://lots.social/business | ICP 1 |
| For agencies | https://lots.social/agencies | ICP 2 |
| API & MCP | https://lots.social/api | ICP 3 |
| Pricing | https://lots.social/pricing | All |
| Help centre | https://lots.social/help | All |
Legal: /terms-of-service · /privacy-policy · /refund-policy · /cookie-policy
That is the whole indexed site. All six above plus the four legal pages return 200; the sitemap lists exactly these plus the markdown mirrors.
Link to the segment page, not always the homepage. An agency-targeted post should land on /agencies.
Retired — do NOT link to these
Removed on 8 Sep 2026; they now 308-redirect and are correctly absent from the sitemap:
| Old URL | Now redirects to |
|---|---|
/about | https://lots.social |
/press | https://lots.social |
/careers | https://lots.social |
/affiliates | https://lots.social |
/contact | https://support.lots.social/contact |
/status | https://status.lotstech.com/ |
There is no press kit page any more. If a journalist asks for assets, send the files listed below and point them at contact@lotstech.com. Do not promise a press page.
There is no affiliate programme — the page is gone and the programme was never live.
Machine-readable mirrors — for agents, and for pasting into a chat
| URL | What |
|---|---|
https://lots.social/llms.txt | Index, ~700 tokens — start here |
https://lots.social/index.md | The product |
https://lots.social/business.md | Business-owner argument |
https://lots.social/agencies.md | Agency argument |
https://lots.social/api.md | Developer argument |
https://lots.social/pricing.md | Live prices — quote this, never a remembered number |
https://lots.social/llms-full.txt | All of the above in one fetch |
Same facts as the HTML at roughly a thirtieth of the tokens, and the pricing inside is read from the billing catalogue at request time. Each HTML page advertises its mirror via <link rel="alternate" type="text/markdown">.
Developer surfaces
- MCP server:
https://api.lots.social/mcp(405 on GET — it is POST-only, that is correct) - REST base:
https://api.lots.social - Docs + OpenAPI 3.0:
https://api.lots.social/docs - MCP docs:
https://api.lots.social/docs/mcp - API keys and dashboard:
https://api.lots.social/dashboard
Other properties
- Blog:
https://blog.lots.social - Support:
https://support.lots.social/contact - Status:
https://status.lotstech.com - Contact email:
contact@lotstech.com - Agent by email:
lots-social@lotsagent.com(from your account address) - Telegram bot:
@LotsSocialBot(one-time connection)
Sibling products — one login, one credit balance
LotsAgent lotsagent.com · LotsBlog lots.blog · LotsLink lots.link · LotsCommerce lotscommerce.com · LotsTeam
Show LotsAgent, LotsBlog, LotsLink and LotsCommerce to business and agency audiences — all four are legible to them. LotsTeam is founder tooling with a single audience; leave it out of business- and agency-facing material.
Social handles
@lotssocial on X. Facebook, Instagram and LinkedIn accounts are configured in the site (facebook.com/lotssocial, instagram.com/lotssocial, linkedin.com/company/lotstech). These are configured, not verified as active — check the account exists and is live before pointing anyone at it or citing a follower count.
Images and media
| Asset | Path | Notes |
|---|---|---|
| Share card — default / home | /og-home.jpg | 1200×630 |
| Share card — business | /og-business.jpg | 1200×630 |
| Share card — agencies | /og-agencies.jpg | 1200×630 |
| Share card — API | /og-api.jpg | 1200×630 |
| Logo | /logo.png | |
| Favicons | /favicon-96x96.png, /favicon.svg, /favicon.ico | |
| Founder photo | /sivaguru.jpeg | Portrait — crop from the shoulders, not square; a square crop takes the top of his head off |
| Demo video | /lots-social-demo-for-website.mp4 | ~2 minutes |
All four share cards are exactly 1200×630 (1.91:1) — the ratio every network lays out from, and the numbers are hardcoded in the page metadata. If you make a new one, match that size or the card letterboxes even though the file is fine.
/lots-social.jpg is retired. It shows a two-versions-old headline, the removed Email/Telegram surfaces, "12+ platforms", and a "FREE to start" stat that misstates the pricing. Do not use it anywhere.
Naming and brand
- Product:
LotsSocial— one word, capital L and S. Never "Lots Social", "lotssocial", or "LotsSocial.com". - Company:
LotsTech AI Solutions Private Limitedon first legal mention,LotsTechafter. lots.socialis the address, not the product name. Don't use them interchangeably in a sentence.- Copyright line:
© 2026 LotsTech AI Solutions Private Limited. All rights reserved. - Brand blue
#2563EB· dark ground#0A1020· page tint#F7F9FF - Company D-U-N-S: 772073652
Re-check schedule
Verify this note's links whenever a page is added or removed, and at minimum before any press, directory submission or launch push. Update the date at the top when you do.
8. Business Constraints & Goals
Checklist note 8 of 9. Living document — status below is dated; check it before relying on it. Read the "must not claim" section before publishing anything.
Situation — as of 21 September 2026
The product is built and live at lots.social. Marketing starts today, and lots.social is the only product getting marketing attention. There are no customers yet.
- Stage: pre-launch / just-launched. No launch date fixed, no Product Hunt launch decided.
- Team: one founder-developer, plus interns starting on agent-assisted tasks. Everything — product, marketing, support — runs through one person.
- Budget: assume none for paid media. Prefer channels that cost time, not money.
- Geography: English-language, global. Company is in India; pricing is USD with INR credit purchase. No geo restriction on who can buy.
- Analytics: GA4 live (
G-59VKN25YQM). Customer.io for lifecycle messaging. LotsCRM is the pipeline of record from 21 Sep 2026. No attribution stack. - GTM state of record: the lots.team product journey for the LotsSocial project. Not the LotsNotes markdown mirror, not a local folder.
- Site surface shrank on 8 Sep 2026 —
/about,/press,/careers,/affiliates,/contactand/statuswere removed and now redirect. The live marketing site is/,/business,/agencies,/api,/pricing,/helpplus four legal pages. See note 7.
Primary goal
Signups, and their activation into connected accounts. Not traffic, not followers, not impressions. Everything above signups is a leading indicator.
Conversion path
Content or search → segment landing page (/business, /agencies, /api) → signup (no card) → connect an account → publish a first post → trial or credits → paid.
No sales motion. Self-serve only. There is no demo call, no sales team, no "contact sales" — and there should not be. If copy implies one, it is wrong.
Things marketing must NOT assume or promise
This is the most important section in this space. Several plausible-sounding claims about LotsSocial are false, and some have shipped before.
No social proof — none
Absolutely forbidden until this note says otherwise: testimonials or customer quotes · customer logos · "trusted by" · user/post/account counts · "join thousands" · case studies · before/after results · star ratings or review counts · G2/Capterra badges · revenue, growth or funding figures · "loved by agencies" · "#1 anything" · awards · "as featured in".
If a brief asks for a testimonial section, refuse and say why. Substitute from the proof points in note 1: the live product, the mechanism, the verifiable pricing model, the inspectable MCP server and OpenAPI spec, the 14-day guarantee, the founder.
Never claim to be the only one
Adopted 21 September 2026. No "nobody else has this", "the only", "the first", "unique", "no one can" — not in prose, not in a heading, not as a column of crosses in a comparison table.
Why: AI coding agents made shipping fast enough that an exclusivity claim is true for a quarter and embarrassing afterwards. It fails loudly, because it was stated loudly — one competitor page disproves it in front of whoever is reading. Monitoring it would be a cost we carry forever and still lose.
What happened: two published "nobody else has this" claims — a hosted MCP server, and saved brand context reused by app, agent and API — were both found false on competitors' own pages inside one research run. At least seven direct substitutes ship an MCP server, and Metricool includes one on its free plan. The row was removed from lots.social/#compare the same day. See note 5.
Say instead: the shape of the thing, which stays true on the day a rival ships the same feature. "Brand context is one stored object that the app, the agent and the API all read" is defensible indefinitely. "Nobody else has saved brand context" was false within a quarter.
Claims about a named competitor's absence need a link to the page that documents it. "We could not find it" is not documentation — that gets "partial" and a note, or it does not ship.
False claims — do not make these
| Do not say | Say instead |
|---|---|
| "Nobody else has this" / "the only" / "the first" / "unique" | The shape of what we built — see the section above. Never exclusivity. |
| "Posts for you automatically" / "set and forget" / "autopilot" | "Ask for a month and it drafts them — you approve, it publishes." |
| "It fills your calendar with posts" | Nothing produces work unasked. The line is who initiates, not how much gets made. |
| "12+ networks" / "and more" / "growing list" | "12 networks" — it is exactly twelve |
| "ChatGPT can't publish to your accounts" | False — it can, through our MCP server. Corrected twice. See note 3. |
| "We have an MCP server and they don't" | False. Buffer, Hootsuite, Postiz, Postplanify, OneUp, Metricool, Planable, SocialPilot and Vista Social all ship one. Claim we have it, never that others lack it. |
| "Recurring posts" / "repeating instructions" | Parked and unreachable — don't mention |
| "White label" / branded client portal / custom client domain | "A workspace per client with its own context and approvals" |
| "Enterprise plan" / "custom pricing" / "contact sales" | "Above Agency you add credits" |
| Any network outside the 12 | — |
| Any endpoint, tool name or tool count | Describe by category; link https://api.lots.social/docs |
| A price from memory | Fetch https://lots.social/pricing.md |
| A competitor's price from memory | Fetch their own pricing page and date the check |
| A per-account price derived across plans | See note 6 |
A link to /about, /press, /careers, /affiliates | Those pages are gone — see note 7 |
| The affiliate programme as live | It never launched, and the page has been removed |
Safe claims — the code enforces these
12 networks · unlimited workspaces, brands, team members and posts on every plan · billed on connected accounts and media storage only · a subscription is not required · approval-first on every path including API and MCP · purchased credits never expire · one credit balance across every LotsTech product · hosted MCP server with OAuth 2.1 + PKCE · REST API on the same registry · 7-day free trial · 1,500 signup credits, no card · 14-day money-back guarantee for first-time subscribers.
Each of these is a claim about us. None of them says anything about anyone else, which is why they are safe.
When unsure
Fetch https://lots.social/llms-full.txt and check. If it is not stated there or in these notes, do not claim it — write around it or ask. A missing claim costs a sentence; a false one costs trust and may cost a refund.
Available channels
Ranked by leverage for one founder with no budget.
- AI answer engines and agents — highest leverage, lowest competition. Buyers increasingly ask ChatGPT/Claude/Perplexity what to use.
/llms.txtand the.mdmirrors exist for this. Submit to MCP directories and awesome-lists. - Search — the compounding asset. Comparison pages, alternatives pages, per-network guides.
- LinkedIn — the agency channel, and where founder build-in-public content belongs.
- Reddit and communities — r/socialmedia, r/agency, r/smallbusiness, r/Entrepreneur, r/ClaudeAI, r/mcp. Participate for weeks before mentioning the product, always with disclosure. A promotional post here does lasting damage.
- X / Twitter — developers and AI circles.
- Directories — Product Hunt, AlternativeTo, SaaSHub, G2/Capterra, MCP and AI tool directories. One-time effort, long tail.
- YouTube — short demo clips; the product is the proof.
- Email — no list yet; build from signups and content.
Deliberately not doing yet: paid ads (not before the message is validated) · influencer or affiliate programmes · cold outbound at scale (a spam complaint against a company selling social publishing is asymmetrically bad) · Facebook/Instagram organic as an acquisition channel (buyers are there but don't discover B2B tools there — use it for presence and dogfooding).
Dogfooding: our own accounts should be run on LotsSocial, visibly. It is a live demo, a credibility argument, and the fastest way to find bugs.
Realistic cadence for one person: ~1 substantial blog/comparison piece a week, 3–5 LinkedIn posts a week, daily-ish X during build-in-public phases, a demo clip a fortnight. Do not plan a cadence nobody can hold — a channel that goes quiet reads worse than one never started.
Content angles that work pre-launch
The unglamorous middle of social work (SMB) · agency economics and seat costs · AI that doesn't embarrass you · agents and MCP · building in public (our most credible asset right now).
Note on the MCP angle: it is good content ground because the audience cares, not because it differentiates us. It no longer does. See note 5.
High-intent SEO formats: LotsSocial vs [Buffer|Hootsuite|Later|Publer] · [competitor] alternatives · best social media tool for [segment] · how to post to [network] from [Claude|ChatGPT|an API] · per-network guides for the under-served ones (Google Business, Bluesky, Mastodon, Threads).
The long tail of "alternative to X" pages is Ranker's, and it is worth building. Competitors run thirty or more, down to names nobody would call a real rival, because the value is the query volume attached to each name. That is a search play, not a statement about who we compete with.
SEO/AEO infrastructure already built — do not rebuild
Self-referential canonicals, unique titles/descriptions, own openGraph/twitter on every indexed page · FAQPage + WebSite + WebPage + Organization + SoftwareApplication + BreadcrumbList + AggregateOffer structured data · 1200×630 share cards · robots.txt and sitemap.xml including the markdown mirrors · GA4.
Honest assessment of the AEO bet: Claude-family and coding agents do fetch markdown; ChatGPT's and Perplexity's retrieval currently do not negotiate for it, and no lab has confirmed reading /llms.txt. It is cheap insurance and a token-efficiency win, not a proven ranking channel. Don't oversell it externally.
Metrics and definitions
In order of importance: 1) signups, segmented by landing page · 2) segment-page reach (if all traffic sits on / and never routes, the homepage router is failing) · 3) signup → connected account (the real activation gate) · 4) connected account → first published post · 5) trial→paid and credits purchased · 6) organic search impressions/position · 7) .md and llms.txt fetches (the AEO bet paying off, and a number almost nobody else can report).
Definitions not to fudge:
- User = an account with at least one connected social account. A signup is not a user.
- Active = published in the last 30 days. Always state the window.
- Customer = paying, by subscription or credits. A credits-only customer has no subscription row, so counting subscriptions alone undercounts.
- Lead = someone who deliberately gave an email. A page view is not a lead.
Reporting rules: never invent a number — "not instrumented" is a useful finding · always name the window and source · at small volumes 3→9 is six people, not 200% growth · no vanity metrics as headlines · label forecasts as assumptions.
The August 2026 baseline, so nobody re-learns it: 37 posts on the LotsSocial brand produced 28 views and 0 website clicks; roughly 180 posts before that produced about 1 click. Zero people outside the founder have used the product. Publishing into an account with no audience was the cause, not copy quality. Any plan whose first move is "post more" is repeating a measured failure.
Known trap: NEXT_PUBLIC_GA_MEASUREMENT_ID must exist at build time on Cloudflare or the GA tag silently vanishes from production. If analytics go quiet after a deploy, check that first.
Update this note when
The first real customer or testimonial exists · a launch date is set · paid channels open · anything new is instrumented · pages are added or removed · the founder's constraints change.
9. Customer Research / Voice of Customer
Checklist note 9 of 9. Living document — never "finished".
Status: EMPTY. This is the honest state.
As of 8 September 2026 there is no customer research, because there are no customers. No interviews, no support chats, no reviews, no sales calls, no onboarding sessions, no churn conversations.
Everything about our customers elsewhere in this space — the vocabulary tables in note 2, the triggers and objections in note 3 — is hypothesis derived from the founder's judgement and the product's design, not evidence. It is written in customers' voice because that is how it should read, but nobody has said any of it to us yet.
Do not quote anything from this space as something a customer said. Do not write "customers tell us…" or "we hear again and again…". Until this note has real entries, we have no customer voice.
What to capture, and where it comes from
Fill these in as the sources become available. Verbatim beats paraphrase every time — the exact words are the asset.
1. How they describe the problem
Their sentence, not ours. This is the highest-value thing on the page: the closer headline copy is to the words a real customer used, the better it converts.
Source: first calls, signup survey, support chats, Reddit and community threads where people describe the pain unprompted.
2. Why they signed up
The trigger, in their words. What happened that week?
Source: a one-question onboarding survey — "what made you look for something like this today?"
3. Why they did NOT sign up / did not convert
The most valuable and least collected. What stopped them at the pricing page or the connect screen.
Source: exit intent, a reply-to email after a lapsed trial, direct outreach to signups who never connected an account.
4. What they switched from, and why
Which tool, what broke, what finally moved them. Feeds the battlecards in note 5 directly.
5. What they love / what frustrates them
Especially the small things. Frustrations become the roadmap; loves become the copy.
6. Unexpected use cases
People using it for something we did not design for. Historically the source of the best positioning shifts — watch for these.
7. Churn reasons
Stated and inferred. Distinguish "it didn't work" from "my situation changed".
8. The words they use for our concepts
Extend note 2's vocabulary tables with real language as it arrives, and mark which are verified vs still hypothesis.
How to start collecting — cheapest first
- A single onboarding question — "What made you look for this today?" Free text. One question converts; five do not.
- Reply to the first 20 signups personally. One founder is an advantage here: a real reply from the person who built it gets answers a survey never will.
- Read communities for verbatim pain. r/socialmedia, r/smallbusiness, r/agency. Do not promote — collect language. This is the only source available before we have users, and it is legitimate research.
- Log every support conversation somewhere retrievable, and mine it monthly.
- Ask lapsed trials one question — "what stopped you?" — with no pitch attached.
- Competitor reviews on G2/Capterra/Reddit. What people complain about in Buffer, Hootsuite and Later is a direct read on what our segment values.
Entries
Append below. Date each one, name the source, and quote verbatim. Keep the customer's own words in quotation marks; keep your interpretation clearly separate.
Format:
```
YYYY-MM-DD — [source: onboarding survey / support / call / community]
Segment: business owner | agency | builder
Verbatim: "…"
What it tells us:
Action taken:
```
(No entries yet.)
When the first entry lands
Real customer language should immediately propagate: update the vocabulary tables in note 2, the objection wording in note 3, and — once there is a named customer with permission — lift the social-proof ban in note 8. That ban is the default, and only this note's evidence can lift it.