Back to Index
EurekaGO Brand Playbook
11
Templates &
Stationery

EurekaGO templates system — email, email signature, presentations, and business cards.

Document 11 / 12 Version 1.0 · May 2026 Confidential
A — Overview
One brand.
Every surface.

Templates are not convenience tools — they are brand enforcement at the point of contact. Every email sent, every deck presented, every card handed over is a brand expression. These templates define what that expression looks like in each context, removing ambiguity and eliminating off-brand improvisation.

01
Email Templates
Structure, tone and format for external and internal email communication.
02
Email Signature
Consistent signature block for all team members, with variants by role.
03
Presentation Template
Slide architecture, type scale, and layout grid for all decks.
04
Business Cards
Print specifications, layout rules, and front/back structure.
A template is not a shortcut. It is a constraint that protects the brand from well-meaning people having a bad day.
B — Email Templates
Emails that read
like EurekaGO.

Every external email is a micro-pitch. It either reinforces the brand or erodes it. The template below defines the structural zones of an outbound email — from subject line to signature — with precise rules for each layer.

Email rules — Always
Subject line: specific, not clever. State the value proposition.
Preview text: extends the subject, never repeats it.
Max 4 structural zones. One CTA. Zero ambiguity about the next step.
Numbers in the body: concrete and verified (190k, 980 — not "thousands").
Sign off: name + role only. No "Best regards." No "Hope this finds you well."
Language follows context: Italian for Italian contacts, English for international.
Email rules — Never
No exclamation marks. Not in the subject, not in the body.
No "I hope this email finds you well" or equivalent opener.
No passive voice in CTAs ("Feel free to reach out").
No more than one link or CTA per email.
No bullet lists with 6+ items. If it takes a list, it takes a deck.
No unsolicited attachments on a first contact email.
C — Email Signature
The signature
is a brand asset.

The email signature is seen by every person we communicate with. It carries name, role, and brand identity in a fixed 4-line structure. No custom flair, no added graphics, no team-specific variations beyond the role line.

STANDARD SIGNATURE — ALL ROLES
First Last
Role Title, EurekaGO
GO
The infrastructure layer for vertical product data.
Email firstname.last@eurekago.it
Web eurekago.it
LinkedIn linkedin.com/company/eurekago
eurekago.it
Variant A
Standard
Used by all team members. Full 4-section block: name/role → divider → company/tagline → contacts. No photo, no social icons, no banners.
Variant B
Vertical (BIKE)
For team members working exclusively on eureka!BIKE. Company line reads "EurekaGO — eureka!BIKE". Web link points to eurekabike.com. All else identical.
Variant C
Minimal
Minimal
For internal comms and replies. Name + role + eurekago.it. No tagline, no contacts block. Used only in thread replies, never on a first contact email.
Signature rule
No custom banners. No "Confidentiality notice" footers unless legally mandated. No seasonal additions. The signature does not change — not for Christmas, not for a product launch, not for a campaign. It is infrastructure, not decoration.
D — Presentation Template
Decks that carry
the system.

Every EurekaGO presentation follows a fixed slide architecture. Six slide types cover all scenarios — from cover to close. Each type has a defined layout, a defined color role, and a defined information hierarchy. No slide should be improvised from scratch.

01 — Cover
EurekaGO
System Overview
01
02 — Section divider
The Problem
02
03 — Content
One normalized
dataset. All layers.
04 — Data / Proof
190k+
Products
normalized
05 — Quote / Statement
"The data is normalized once. It propagates everywhere."
Core positioning — EurekaGO
06 — Close / CTA
eurekago.it
hello@eurekago.it
Slide rules — Always
One idea per slide. If it needs two paragraphs, it needs two slides.
Numbers lead data slides — large, left-aligned, azure. Label below in small caps.
Ghost page number bottom-right: 280px, ink, 0.12 opacity.
Footer: brand name left, slide number right. Every slide except cover and close.
Section dividers: always azure background, white title, no body copy.
Font: Archivo throughout. Title 40–52px / 900. Body 16–18px / 400–500.
Slide rules — Never
No gradient backgrounds except on cover (subtle, brand-approved).
No clip-art, stock illustrations, or decorative icons.
No bullet list slides with more than 4 items.
No custom typefaces — Archivo and JetBrains Mono only.
No "thank you" closing slide. The closing slide carries the CTA and URL.
No animation beyond a single fade-in transition between slides.
E — Business Cards
The card is the
first impression.

Two sides. Front: the person. Back: the brand. The format is fixed — no custom color choices, no photographic elements. Portrait orientation. Every card across the team reads as one system.

GO
Jacopo Vigna
Founder
jacopo.vigna@eurekago.it
eurekago.it
+39 348 438 1018
CASALGRANDE (RE), IT
TORRANCE (CA), US
GO
AI-driven data systems
Format
55 × 85 mm
Portrait / vertical format
Paper
400 gsm
Uncoated, matte — no lamination
Finish
Spot UV
Logo wordmark on front only
Bleed
3 mm
All four sides, safe zone 4 mm
Card rules — Always
Front background: Ink (#0A0A0A). Back background: Cream (#F5F3EC).
Name in Archivo 900, role in uppercase tracked label below.
Contact info: email + website + phone only. No social handles on the card.
Back carries brand wordmark only — no additional messaging.
Card rules — Never
No QR codes. The URL is the QR code.
No color variations by department or vertical.
No photography or illustration on either side.
F — Document Templates
Documents that
mean business.

Three document types cover the full commercial and operational lifecycle: the proposal (selling), the brief (briefing), and the report (delivering). Each follows the same structural logic — brand identity at the header, content in body, version and confidentiality in the footer.

Template 01
Proposal
Used in commercial contexts — partner onboarding, investor conversations, B2B sales. Problem-first structure. Numbers in the body. One CTA at the close.
Cover Problem statement + EurekaGO positioning
Context Why this company, why now
Solution Module or service being proposed
Proof Numbers, case, or reference
Terms Pricing, timeline, next steps
Close CTA + contact
Template 02
Brief
For internal alignment, agency handoffs, or partner project kickoffs. Defines scope, constraints, and success criteria before any work begins.
Objective One sentence. What is this brief trying to achieve?
Context Background, constraints, dependencies
Scope What's in / what's explicitly out
Deliverable Format, deadline, owner
Success How we measure it
Template 03
Report
Periodic or milestone-based. Used for internal leadership reviews, partner performance readouts, or post-project retrospectives. Data-led, no narrative filler.
Summary 3 bullet points max. Key findings.
Data Charts, tables, numbers — no prose proxies
Analysis What the data means, not what it shows
Actions What changes as a result — owner + date
Appendix Raw data, methodology notes
Header: EurekaGO wordmark left, document title right. Footer: version number left, confidentiality label center, page number right. These three elements are non-negotiable on every page.
G — Anti-Patterns
What a EurekaGO
template is not.

Templates fail in predictable ways. These are the most common failure modes — patterns that emerge when brand discipline is traded for personal preference or short-term convenience.

Critical
The Off-Brand Deck
A presentation built from scratch in a different font, a different palette, or a personal template downloaded from the internet. This happens when templates are not distributed before they are needed. Templates must be available before anyone opens a blank file.
Critical
The Custom Signature
"I added my photo." "I put a campaign banner in mine." "I prefer a different font." The signature is not a self-expression surface. It is the brand's final word in every email thread — it must be identical across the team.
Avoid
The Email That Needs a Deck
A 600-word email with six bullet sections and three attachments. If it requires that much structure, it requires a deck. Emails persuade — they do not inform at length. Long means wrong format.
Avoid
The Card with a QR Code
Adding a QR code to the business card is a symptom of not trusting the URL to do its job. The URL is the call to action. The card is not an app. If someone wants to contact you, they can read a URL.
Avoid
The Animated Deck
Fly-in text, spinning data charts, 10-second intro animations. Animation in decks signals that the content is not strong enough to stand alone. One cross-fade between slides. That is the limit.
Avoid
The Document Without Versions
A proposal sent without a version number is a prop