Docs/brand messaging brief - #312
Merged
Merged
Conversation
…rief Marketing agencies reviewing LibreDB found no brand story and no value propositions on any public surface. The brief that answers them is built proof-first: this is the evidence layer, written before any prose so that no promise can be drafted without something behind it. Every row carries the date it was checked, because provider counts, channel counts and competitor editions all drift. Two claims carried from an earlier review did not survive re-verification and are recorded as dropped rather than quietly removed.
The story opens on the moment that started the project: a database ready in forty seconds and an afternoon spent finding a way to look inside it. The second scene multiplies that across a polyglot team and a new joiner, which is where the cost becomes visible. The belief that the tool goes to the data is then followed to its consequences, so that MIT reads as a requirement of the architecture rather than a gesture, and the paid Platform stays coherent beside it.
Three doors into one claim, each carrying audience, pain, promise, proof and difference. Writing them surfaced four promises with no evidence behind them, so ER diagrams, the AI layer, role separation and destructive-statement analysis were verified and added to the proof library rather than asserted. The door ordering is recorded with its reason: leading on the Enterprise-wall argument would hand our credibility to another company's pricing page.
Three audience layers with the register each requires, ordered by how adoption actually flows: the engineer tries it, the lead evaluates it because of that, and the PaaS layer stays documented but dormant. The honesty limits name the four gaps and three temptations explicitly, so display masking stays a presentation feature, engine-count leadership is never claimed against a competitor that bundles more SQL drivers, and comparison stays on licence and scope with sources attached.
…ion map Three taglines offered as options rather than a decision, and a surface-by-surface map saying which door each one leads with. The map records the GitHub About line as a defect to fix first: it names four engines against ten shipped.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Type of Change
Related Issue
Closes #
Changes Made
Testing
Test Environment
Screenshots (if applicable)
Checklist
Additional Notes