Calm, intelligent, principled.
This is the working source for voice, tone, terminology, and UX copy across PocketSeed. It's how we talk to users, especially new ones encountering the platform for the first time.
What we're trying to do
PocketSeed is structurally complex, but the underlying idea is human: companies say things about themselves, and now there's a way to manage and back them up. We want PocketSeed to make managing a brand's voice feel exciting and achievable, helping teams be bold while staying inside the lines on risk and reward.
We're not asking anyone to change what they do. We're giving them the structure and confidence to keep doing it, loudly.
Who we're for
Sustainability-led brands. Small to medium, cross-functional, often with one person wearing several hats, the marketing or comms manager who's also watching regulation, owning brand tone, and chasing evidence from suppliers. They're already doing the hard part. We make their existing work defensible.
Agencies and consultants who do the evidence-gathering on behalf of clients. They produce the proof; their clients make the claims.
Internal teams. Marketing, sustainability, legal, comms, aligning on what can credibly be said.
Brand voice
We are calm, intelligent, and principled, not corporate or preachy.
We exist because responsible teams are tired of navigating claims through email threads, PDFs, and fragmented approvals. We don't amplify noise. We bring structure to it.
We speak clearly and directly. We avoid hype, fear, and inflated promises. We don't moralise. We don't shame. We help.
We sound like the colleague who understands both the creative ambition and the regulatory reality, and helps you bridge the gap.
- Confident
- Structured
- Modern
- Professional
- On their side
- Aggressive
- Bureaucratic
- Trendy
- Stiff
- Above them
We don't claim to "change the world." We help teams say what they mean and stand behind it. We believe claims should be built, not just written. We believe trust should be structured, not assumed.
Closest references
Stripe · Notion · Patagonia's environmental reporting. We are not an audit firm, a regulator, or a compliance platform.
The four pillars
Each pillar should be felt in the product experience and reflected in the copy.
Pillar 01Guidance
We help teams navigate complexity.
PocketSeed walks users through a process that would otherwise be confusing, fragmented, or easy to get wrong. The product is a guide, structured, supportive, oriented around the user's needs. We're not a destination, we're a path.
Pillar 02Intelligence
Structured reasoning that surfaces what matters.
The framework analyses claims, identifies gaps, provides detailed insight from multiple angles. We bring rigour to something that previously relied on instinct and luck. The product thinks carefully so the user doesn't have to start from scratch.
Pillar 03Integrity
Claims built to withstand scrutiny.
Integrity is the core promise. Not that claims are always right, that they're built honestly, with evidence, through a process the user can stand behind. The user is accountable, and PocketSeed gives them the tools to earn that accountability properly.
Pillar 04Flow
Replace chaotic email chains with composable evidence.
The practical, day-to-day value. PocketSeed replaces the scramble, email threads, missing documents, back-and-forth approvals, with a calm, organised process. It aligns teams around evidence and makes everyone's life easier.
Core principles
These shape every line of UX copy.
Supportive, not judgmental
PocketSeed helps companies do things properly. It doesn't punish mistakes or assume bad intent. Many companies are doing meaningful work, the systems around claims are messy. We exist to fix that, not to call it out.
Make them the hero
The marketing manager spotted the problem. They're fixing it. Everyone around them benefits. PocketSeed gives them the tools, they get the credit. Reinforce that they're doing something smart and proactive, not something they were forced into.
Opportunity, not obligation
Don't frame PocketSeed as damage control. Frame it as a competitive edge, the ability to say bold things and genuinely back them up. Lead with what they gain. Protection is a benefit, not the point.
Evidence without accusation
Evidence and defensibility are central, but always framed as empowering, not enforcing.
Good faith, not perfection
Users don't need to be right forever. They need to be honest about what they knew when they said it. If things change, they update. The record of what they knew then is the protection. This is a liberating idea, not a scary one.
Practically useful
The platform should feel useful in day-to-day work, not just important in the abstract. Show that it helps teams organise documents, reduce back-and-forth, prepare evidence, collaborate across teams, and publish clear records. It's not just about trust, it's about making work easier.
Quiet optimism
PocketSeed should feel hopeful about progress, not cynical about greenwashing. Lead with what's gained. When context calls for it, it's fine to acknowledge harder reality, but keep it as the supporting note, not the headline. Risk acknowledged, never weaponised.
Teach as you go
Don't front-load jargon. Earn each term by explaining the concept first. Users learn "claim", "evidence", "credential", and "product" by doing, not by reading a glossary.
The three-beat story
When in doubt, structure copy around this arc:
We help you get it right
The framework guides you, surfaces gaps, asks the right questions.
You sign off
Accountability is yours, and that's a feature, not a bug.
We issue the credential
A permanent, timestamped record of what you said, why, and what backed it up. Yours to share.
Terminology
Use these consistently, the load-bearing vocabulary of the product.
Credential the core thing PocketSeed creates
A data package that locks together a claim's content, its supporting evidence, the sign-off, and a timestamp, as one record. Tamper-proof, on-chain timestamped, shareable.
PocketSeed certifies the integrity of the package, not the truth of the claim inside it. Lead with what credentials enable (a permanent, shareable record). The technical proof points are accurate and available when relevant, especially around sharing, but shouldn't be the opening line.
Claim what gets said
What a company says about their brand, products, or practices, the public-facing statement built on top of a credential. Co-equal with credential: the credential is the underlying data package, the claim is what gets said based on it.
Introduce it by meeting users in their own language first ("the things you say about your products") before using the word directly. Claim is the product term.
Product a bundle of credentials
A way to bundle credentials and product information together so they can be shared as one item. Useful when a single product has multiple credentials behind it (sourcing, manufacturing, sustainability) and the team wants to keep and share them as one.
Evidence what backs a claim up
Certifications, lab reports, supplier contracts, test results. Use real-world names where possible; refer to the category as evidence. Reserve certificate for actual third-party certifications (ISO, B Corp, Fair Trade); never for the things PocketSeed itself issues, those are credentials.
Sign-off the user's mark
What the user does when they're satisfied a claim is ready. They're the ones accountable. This is a feature, not a burden, it's their name on something they're proud of.
CLEAR Framework working name
How PocketSeed guides users through building a responsible claim. It surfaces gaps, asks the right questions, suggests improvements, and gives an overall score. It doesn't verify the claim for them, it helps them verify it themselves. Accountability stays with the user.
Snapshot the metaphor for a credential
A claim was made, evidence was attached, someone signed off, all on a specific date. If circumstances change later, the snapshot shows what was known and intended at the time. The protection isn't that you're always right, it's that you were always honest.
Words to avoid
Lead with these only when they earn their place, around sharing, exporting, or proof moments. Never in the first line of an onboarding screen.
Quick reference, when writing
Before shipping a piece of copy, run it past these:
- Does this make the user the hero, or talk down to them?
- Does this lead with what they gain, not what they avoid?
- Have we earned each term, or front-loaded jargon?
- Are we calm and principled, or hyped/fearful?
- Could this sit comfortably in a Stripe / Notion / Patagonia interface?
- If it's onboarding copy, does it avoid "compliance / audit / verified-as-stamp"?
- Does it pass the colleague test, does it sound like a knowledgeable peer, or a regulator?