TISSA Consulting
Web Blueprint — directional web architecture and vendor handoff pack

Web Blueprint

Architecture before construction. Directional web architecture, sitemap, IA, and a vendor-ready RFQ — so you know exactly what to build before anyone writes a line of code.

The architecture pause

Define the site before you build it — or before you hire anyone to.

Most website projects fail before a developer opens their editor. Without a spec, briefs are vague, vendor quotes are incomparable, and the first revision round costs more than the Blueprint would have. The Web Blueprint is the pause before that build — three to four weeks of principled architecture that turns a vague idea into a precise, vendor-ready brief.

You get two documents — a Blueprint Deck that defines the directional architecture, sitemap, IA, and wireframe-level direction, and an RFQ / Vendor Handoff pack that any qualified developer or agency can quote against without a second call. The Web Blueprint does not build your site. That is the purpose of the Website Development & E-commerce add-on — and the Blueprint feeds directly into it.

The Blueprint uses your Brand Master Book as its primary input — every information architecture decision traces to a brand position, not a design trend. If you don’t have a Master Book yet, the Blueprint can still be scoped; it will reference your existing materials and flag the gaps.

What you get

Two deliverables.
One spec any vendor can build against.

A directional Blueprint Deck and a vendor-ready RFQ — no development work included, no lock-in to any builder.

Blueprint Deck

The directional architecture document. Covers the objective, sitemap, page-by-page IA, wireframe-level layout direction, and brand governance notes drawn from the Master Book — everything a design or dev team needs to begin.

Format
01 · The architecture

Principal-authored, brand-traceable. Every IA decision tied to a position in your system — not a trend, not a template.

Format PDF · Slide deck format

RFQ / Vendor Handoff Pack

A vendor-ready Request for Quotation package. Scope summary, technical requirements, CMS recommendations, performance benchmarks, and brand compliance criteria — written so any qualified builder can quote accurately without a second call.

Format
02 · The brief for builders

Comparable quotes require a common spec. This is that spec — structured, complete, and free of the ambiguity that inflates dev costs.

Format PDF · Vendor-ready package
Who it’s for

Before you build.
Before you hire.

Two entry points — one outcome: a spec that stands before a vendor touches the keyboard.

Post-BMB clients going to market. You finished the Brand Master Book. Now you need a website that executes the system — but before you talk to a developer, you need a directional architecture they can bid against. The Web Blueprint uses your Master Book as its input and produces the spec your chosen builder works from. It connects directly into the Website Development & E-commerce add-on if TISSA is building it, or travels with you to any vendor of your choice.

Companies that need to specify before they contract. You have an existing brand and you know you need a new site — but you’ve been burned by vague briefs, scope creep, or quotes you couldn’t compare. The Web Blueprint produces the RFQ that ends that problem. You arrive at vendor conversations with a document, not a conversation.

Where it fits

After the Brand Master Book.
Before the build.

The Web Blueprint sits between your brand system and your website build — it does not do both.

BRAND MASTER BOOK

The brand operating system — strategy, visual identity, voice, governance. This is the input the Web Blueprint reads to make architecture decisions. Recommended before the Blueprint; not strictly required.

WEB BLUEPRINT

Directional architecture, IA, sitemap, and RFQ. Defines what gets built — does not build it. The product of this engagement: a spec your builders execute against and a handoff pack vendors can quote from.

WEB DEVELOPMENT & E-COMMERCE

The build. Full web execution — informative, custom, or commerce — governed by the Brand Master Book and built against the Web Blueprint spec. This is where code gets written and sites go live.

How it works

Three to four weeks.
Two documents. One spec.

Kickoff to vendor-ready handoff in three to four weeks. One call to align, one week of research and architecture, one week of production, one handoff — everything documented before a vendor quote is requested.

  1. 1
    Day 0

    Kickoff · 60 minutes

    Business objective, target audience, existing assets, competitive landscape, and site scope — everything we need to architect from your position, not from a template. Brand Master Book ingested here if available.

  2. 2
    Week 1

    Architecture & IA

    We define the sitemap, user flows, and information architecture — every decision traced to the brand system and the business objective. No wireframe design, but wireframe-level direction: what lives where, why, and what each page must accomplish.

  3. 3
    Week 2–3

    Blueprint Deck & RFQ production

    The Blueprint Deck is drafted — directional architecture, per-page IA, and brand governance notes — alongside the RFQ / Vendor Handoff pack: scope, technical requirements, CMS recommendation, and compliance criteria. Both land 24 hours before the handoff call.

  4. 4
    Week 3–4

    Handoff call · 60 minutes

    We walk both documents with you, answer questions, and align on next steps — whether that is the Website Development & E-commerce add-on with TISSA, or taking the RFQ to external vendors. You leave with everything you need to move.

Does the Web Blueprint build our site?

No — and that is the point. The Web Blueprint defines the architecture and produces the vendor-ready spec. The build is a separate engagement: the Website Development & E-commerce add-on, which TISSA can execute once the Blueprint is signed off, or which you can take to any external developer or agency using the RFQ pack.

Do I need the Brand Master Book first?

Recommended, not mandatory. The Blueprint performs significantly better with a Master Book as its input — every IA decision has a brand position to trace to, which keeps the architecture defensible rather than decorative. Without one, we work from your existing materials and flag what is missing. We will tell you honestly if the Blueprint should wait for the Master Book.

What do I do with the RFQ pack after?

Two paths. You give it to TISSA to run the Website Development & E-commerce add-on — no ramp-up, we already know the spec. Or you take it to external developers or agencies to collect comparable quotes. Either way, you arrive at vendor conversations with a document, not a wish list.

Is the $1,500 credited toward the build?

Yes. If you proceed to the Website Development & E-commerce add-on with TISSA within 60 days of the Blueprint handoff, the $1,500 is credited against the first milestone of the build engagement.

PrincipalLuca Baldisseri
Format2 PDFs · 1 handoff call
EngagementWeb Blueprint · Standalone
Edition2026 — Vol. 01
Ready for the pause?

The best time to build your brand operating system is before you need it.

The second best is now.

Schedule a Conversation
+1 (347) 379-3599 Schedule