Relevance
Show the buyer why the offer applies to a problem or situation like theirs.
Trust architecture · publishing principles
Proof should tell you what actually happened.
AtlasFlow does not turn every screenshot into a client case study, use motion to hide meaning, or replace missing outcomes with confident language. The trust signal, search claim and commercial claim all have to survive the same evidence check.
01
AtlasFlow client delivery
Work delivered through an AtlasFlow client relationship.
02
Delivered sprint
A defined AtlasFlow sprint completed for a client.
03
Active engagement
Work currently underway; outcomes must not be presented as final.
04
Strategy / Commercial plan
Analysis or planning work; not presented as implemented delivery.
05
Concept
A proposed or exploratory asset; never presented as live client work.
06
Operating system / Founder-built product
A real system or product associated with founder operating experience; relationship stated explicitly.
07
Owned operating venture
A business AtlasFlow’s founder operates or owns; never presented as independent client proof.
08
Partner / Associated capability
Capability delivered by or with a partner; AtlasFlow’s role must remain clear.
Case-study standard
Context → Constraint → Observation → Decision → Work → Status → Outcome → Lessons.
Metrics appear only when they are documented. If an outcome is qualitative, it is described as qualitative. If evidence is missing, the public claim gets smaller — not louder.
Private evidence belongs in the internal proof vault. The public website only exposes material appropriate for publication.
Inspect the published work →Trust placement standard
Resolve the doubt where the doubt occurs.
Logos, reviews, process detail, pricing, founder identity and case evidence answer different questions. They should sit near the uncertainty they actually reduce.
Competence
Expose the method, capability or operating depth required to do the work well.
Evidence
Place inspectable proof beside the claim or decision it actually supports.
Risk
Make scope, price, process, limits and important responsibilities explicit before commitment.
Continuity
Explain what happens after the click, enquiry, booking or purchase — and who owns the next action.
Search authority standard
Useful authority before content volume.
Search visibility is treated as a consequence of clear entities, original expertise, crawlable structure, useful internal relationships and pages that answer a real commercial decision.
Identity
Keep AtlasFlow, Franco Smit, the canonical domain and business role consistent across visible pages and structured data.
Authorship
Put named human authorship and relevant operating context on original thinking instead of publishing anonymous search content.
Crawlability
Important names, relationships, headings, links and answers remain semantic HTML; animation and interaction are progressive enhancement.
Information gain
Publish only when AtlasFlow can add a useful distinction, framework, evidence, process or first-hand operating perspective.
Connection
Link services, problems, frameworks, evidence, tools and commercial next steps according to the buyer’s next question rather than keyword repetition.
Motion standard
Animation guides attention. It never carries the proof.
Names, relationship labels, headings and internal links remain ordinary HTML even when a carousel or transition changes how they are scanned.
Moving proof pauses on hover or keyboard focus, supports touch interaction and becomes static or manually scrollable when reduced motion is preferred.
Motion must not create layout shift, hide the evidence path or make the important commercial action slower to understand.
Publication rule
Verify → label → contextualise → link → measure.
Before a trust or search claim goes live, AtlasFlow checks the relationship, the support available, the decision the evidence is meant to help and the boundary that must remain visible.