EurekaGO templates system — email, email signature, presentations, and business cards.
Document 11 / 15Version 1.1 · September 2026Confidential
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.
OUTBOUND — PARTNER / PROSPECT
From: Jacopo Vigna <jacopo.v@eurekago.it>
Il catalogo che stai normalizzando ogni giorno — già fatto.
Preview text: 190.000+ prodotti normalizzati, pronti per essere distribuiti.
Zone 1 — Hook (max 2 lines)
Hai 40 brand in catalogo. Ognuno ha il proprio formato. Ogni mese ricevi aggiornamenti che qualcuno normalizza manualmente. Questo è il problema che EurekaGO ha già risolto per 980 retailer italiani.
Zone 2 — Proof point (1 concrete fact)
190.000+ prodotti normalizzati. Una tassonomia verticale sviluppata sul campo. Il dato entra una volta — si propaga su tutti i layer commerciali: B2B, B2C, ecommerce, WMS.
Zone 3 — Relevance (why you, why now)
Stiamo aprendo l'accesso a distributori multi-brand nella rete italiana. Se gestisci un catalogo che vale la pena normalizzare una volta sola, vale la pena parlarne.
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. The wordmark sits on the left, an azure rule divides, and a fixed four-row identity block follows: name, role, tagline, contacts. No photo, no social icons, no banner, no team-specific variation beyond the role line and the vertical.
The three blocks below are the signature itself, rendered at actual size — not a mock-up of it. Copy one, paste it into your mail client, replace the tokens. Everything is inline-styled and table-based because mail clients discard stylesheets and CSS classes.
Variant A
Standard
The default. Every role, every first-contact email, every external thread. Unless you work exclusively on a vertical, this is your signature.
Replies inside a thread that is already running — never a first contact. Set it as the reply signature so it applies on its own, without anyone having to remember. This is the EurekaGO one; variant D is its counterpart for the vertical.
Variant C for anyone on the bike vertical. Same rule: thread replies only, set as the reply signature. Same two differences as variant B — the company line and the web address.
Valiants is the group company, not a EurekaGO vertical, so it carries its own mark, its own azure and its own payoff — and it never appears alongside the EurekaGO lockup. It sits in this chapter because the structure is shared: mark on the left, azure rule, four-row identity block. Addresses follow the same convention on the valiants.it domain.
Role in English — Founder, Head of Data, Software Engineer. One role, no stacked titles.
PHONE
The person's phone, written as +39 348 438 1018. It appears twice: as visible text, and inside the tel: link, where it carries no spaces or brackets (tel:+393484381018).
The phone is optional, and the choice belongs to the person. Without it the row keeps its place and becomes the email instead: label Email, a mailto: link, address per the convention above. The row is never left empty, and never carries both.
Installing it
Click Copy signature on the variant you need. The block is copied as formatted content, with its styling intact — not as source code.
In Gmail, go to Settings → General → Signature, click into the box and paste with Ctrl+V. Not Ctrl+Shift+V: that strips every style and leaves you plain text.
Replace the tokens by typing over them. Do not restructure the block — clicking around inside it and dragging things is how the table gets broken.
Under Signature defaults, assign Variant A (or B) to new emails and Variant C to replies/forwards. Do this per address if you send from more than one.
What the mail client does to it
Survives
Inline style attributes on individual elements.
Table layout, width and bgcolor attributes.
Colours, font sizes, padding, borders, backgrounds.
Images served from an absolute https URL, and links.
Discarded
Stylesheets, <style> blocks, CSS classes.
Web fonts. Archivo cannot be loaded in mail.
SVG, and base64 data: images.
Positioning, floats, pseudo-elements.
Three consequences worth knowing before they look like faults. The font degrades by design: anyone without Archivo installed sees Helvetica or Arial, and Outlook always shows Arial. Images start blocked in most clients, so on a first contact the wordmark is an empty box until the recipient allows it — which is why the signature has to read completely without it, and why the alt text matters. Dark mode has no fix: a black wordmark on a transparent background disappears against a dark canvas, and mail clients ignore prefers-color-scheme. None of this is repairable in code; it is the reason the block carries no information that only the image conveys.
Signature rule
The contact row is one line, never two: a phone number or an email address, whichever the person prefers. 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, portrait, both white. Front: the person, under the full lockup. Back: the brand, carried by one piece of brand art and the two sub-brands beneath it. The format is fixed and nothing on the card is chosen per person beyond the four lines that identify them.
AI-Driven Data Systems
Jacopo Vigna
Founder
jacopo.v@eurekago.it
+39 348 438 1018
eurekago.it
Casalgrande (RE) | IT Torrance (CA) | US
Software House
EUREKASTUDIO
Industry Vertical
EUREKABIKE
Software made with ♥ for detail
Format
55 × 85 mm
Portrait. Trim size, two pages
Bleed
None
Trim equals artboard — nothing runs off the edge
Safe margin
5.5 mm
Narrowest edge in the production file
Colour
CMYK
ICC. No spot plates. Archivo embedded
These four are read from the file sent to print, so they cannot drift. Paper and finish live with the printer, not in the artwork: the current run is 400 gsm uncoated matte, unlaminated. A spot UV pass on the wordmark has been specified in the past — the production file carries no separation plate for it, so confirm it on the order rather than assuming the artwork requests it.
Why the back is illustrated
Doc 00 defines the personality as a trajectory rather than a fixed point: it starts at pirate energy, startup attitude and irreverence toward complexity, and builds toward institutional solidity and earned gravitas. It also fixes the order — the identity must radiate energy before seriousness.
The card is that trajectory, printed on two sides. The front is the far end of it: a lockup, a name, a role, four lines of contact. It earns trust and says nothing about us. The back is where the brand starts from, and it is drawn rather than written because doc 00 settles that too — we show, we don’t pitch.
It stays a character from the system in doc 09 and never becomes a mascot: the enemy is the chaos in the data, never the person holding the card. And it does the one job a business card actually has. A card that looks like every other card is filed and forgotten; a card with a character on the back is remembered, and so is the conversation it came from.
Card rules — Always
Both sides white. White is the canonical EurekaGO surface — Cream is a secondary, editorial surface (doc 02) and has no place on the card.
Front, top to bottom: pictogram, wordmark, payoff, name, role, contacts, locations.
Name in Archivo Black, uppercase. Role uppercase and tracked directly beneath it.
Contacts in this order: email, phone, website. The email is set bold — it is the channel we want used.
Back: one character illustration, the sub-brand lockups, the sign-off line. Nothing else.
The general card lists the studio, for custom work, and the verticals that are live at the time of printing — today EurekaSTUDIO and EurekaBIKE. A vertical that has not launched does not appear.
Fuchsia appears exactly once, on GO in the wordmark. It is the only colour on the card.
Card rules — Never
No QR codes. The URL is the QR code.
No colour variations by department or vertical.
No photography. The back carries drawn brand art, never a photograph.
No social handles, and no second phone number.
No bleed. Nothing on the card is designed to run off the trim.
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 proposal that cannot be corrected, only resent. Version and date in the footer, from the first draft. "Final", "final_v2" and "definitive" are not version numbers.
