Content model
Atoms are the building blocks of Spectare. Each atom is one focused piece of content — a feature, a pricing block, a FAQ answer. Spectare assembles the right combination for each visitor based on their intent, audience, and stage.
Think of an atom as a single answer to a single question a visitor might have. Not your whole homepage — just one thing, written well, for one type of person.
When a visitor arrives on your site, Spectare reads their intent from signals like referrer, UTM params, and page context. It then picks 3 to 5 atoms that best match what they came to find, and assembles them into a personalised page in real time.
A developer arriving from a GitHub link gets different atoms than an executive arriving from a LinkedIn ad — even though they land on the same URL.
Anatomy of an atom
Type
feature · pricing · faq · comparison · howto · case-study · testimonial
Title
A clear, specific headline. Not clever — descriptive.
Content
100–300 words of focused, honest copy. Markdown supported.
Audience
Who this is written for — developer, manager, executive, or your own segments.
Stage
Awareness · Consideration · Decision
Tags + key stats
Tags help the search find this atom. Stats display prominently and anchor credibility.
Seven types cover most of what a B2B or SaaS site needs to say.
What your product does. One capability per atom — not a list of everything.
e.g. "How Spectare classifies intent without cookies" — written for a developer at the consideration stage.
Cost, value prop, or plan comparison. Works best when written for a specific audience.
e.g. "What you get on the Pro plan" — written for a marketing manager at the decision stage.
One question and one honest answer. Target the objections that actually stop people.
e.g. "Does Spectare work without existing traffic?" — for awareness-stage visitors.
Head-to-head with a specific competitor or approach. Be honest about where you lose.
e.g. "Spectare vs Adobe Target for SMBs" — for a manager at the consideration stage.
Step-by-step instructions for a specific task. One task per atom.
e.g. "Adding your first Spectare slot to a WordPress page" — for a developer.
A real outcome for a real customer type. Even hypothetical scenarios work early on.
e.g. "How a SaaS landing page increased trial signups by showing different messaging to agency vs. direct traffic."
A customer quote with context. The context is what makes it match the right visitor.
e.g. "A developer integrating Spectare for a client agency" — tagged for agency + consideration.
Five principles that separate atoms that convert from atoms that just exist.
An atom about pricing should only be about pricing. An atom about a feature should only explain that feature. Spectare assembles atoms together — they don't need to do everything individually.
Choose an audience and a buyer stage before you write. A developer at the awareness stage needs different language than an executive at the decision stage. The same fact, written twice, will convert differently.
100 to 300 words is the sweet spot. Spectare assembles 3 to 5 atoms per page — if each atom is 800 words, the assembled page becomes overwhelming. Write the essential version.
If your atom can support a stat — setup time, price, a conversion number, a before/after — add it. Stats are displayed prominently and anchor credibility faster than prose.
Add 3 to 6 tags describing the topic, use case, or product area. These feed the vector search that finds the right atoms for each visitor's intent.
Ten atoms gives Spectare enough material to meaningfully personalise for different visitor types. This is the list we recommend writing first.
Sign up, create your workspace, and the admin will walk you through the rest.