WebArt AI MVP in development

Your client's brief.
A complete website blueprint.

WebArt AI is being built to transform business requirements into strategy, structure, content and a clear plan for production.

What it does

From conversation to structure.

Raw business information goes in. Structured website intelligence comes out — the decisions a designer or developer needs before they can start, written down and connected to each other.

Inputsraw · incomplete · mixed
  • 01A client email with the “brief” spread across four paragraphs
  • 02Call notes, half of them about the old website
  • 03A list of services that overlaps in three places
  • 04Three competitor links and two “we like this” sites
  • 05A deadline, a vague budget, a strong opinion about blue
  • 06Existing copy nobody is sure is still accurate
Outputsstructured · connected
  • 01Business summary — what the company does, for whom, and why it matters
  • 02Audience profiles — who the site has to work for, and what they need to see
  • 03Positioning and goals — what the website must achieve, in priority order
  • 04Sitemap — pages and hierarchy, each with a stated purpose
  • 05Page structures — sections per page, in order, with intent
  • 06Content and blueprint — drafted messaging and a build-ready planning document

Core workflow

Six stages. Each one feeds the next.

Select a stage to expand it

  1. Everything the client shared, captured in one project: notes, documents, links, constraints and open questions.

    Takes inClient email and documentsCall notesReference links, constraints
    ProducesA single organized projectA list of what is still missing
  2. AI reads the brief and makes the implicit explicit: what the business does, for whom, against whom, and what the website needs to achieve.

    Takes inThe project briefAttached material
    ProducesBusiness summaryAudience profilesGoals and positioning considerations
  3. Positioning, priorities and tone are set down as decisions the rest of the plan can refer to.

    Takes inBusiness analysis
    ProducesPositioning statementPrioritized goalsTone and direction notes
  4. A sitemap and page-by-page section plan that follows from the strategy — every page and section with a stated purpose.

    Takes inWebsite strategy
    ProducesSitemapPage structures with section intent
  5. Draft copy for each planned section, written in the tone the strategy calls for and tied to that section’s job.

    Takes inPage structuresTone notes
    ProducesSection-by-section draft copyHeadline and CTA options
  6. All outputs assembled into one planning document, with notes for design and development.

    Takes inEverything above
    ProducesWebsite blueprint documentDesign and development notes

Initial MVP · in development

What the first version is designed to do.

01 — Project creation

Collect and organize client information.

A project begins with whatever the client gave you. Paste notes, attach documents, add links and constraints — the project becomes the single place where the brief lives.

New projectStep 1 of 2
Client
Northline Architecture
Brief
Hi — so we run a small architecture studio, 14 of us, mostly residential…
call-notes.md3 reference links+ add
02 — AI business analysis

Extract business context, audience, goals and positioning considerations.

The analysis reads the brief the way an experienced strategist would: what does this business do, for whom, against whom, and what does the website need to achieve? Every finding points back to where it came from.

BusinessArchitecture studio, 14 people, residential and small commercial work.from: brief ¶1
AudiencePrivate clients and small developers evaluating a studio before first contact.from: brief ¶2
GoalMake the studio’s approach legible; establish credibility through built work.from: brief ¶2, references
PositioningConsidered, calm, detail-led — explicitly not “every other architect’s site”.from: brief ¶3
03 — AI sitemap generator

Generate a logical website architecture.

Pages and hierarchy derived from the strategy, with a one-line purpose for each page — so the sitemap is an argument, not a list.

  • Home6 sections
  • Projectsindex
  • Project detailtemplate
  • Approach4 sections
  • Services2 children
  • Studio & contact3 sections
04 — AI page planner

Define page sections and their purpose.

Each page is broken into sections, in order, with what the section needs to accomplish. Nothing lands on a page because it was in the template.

  1. 01HeroState what the studio does, for whom.
  2. 02Selected workThree projects showing range.
  3. 03ApproachHow a constrained site gets resolved.
  4. 04ServicesRight entry point for each audience.
  5. 05ContactStart a conversation, low friction.
05 — AI content generator

Generate structured website messaging.

Copy drafted section by section, in the tone the strategy calls for, and tied to the section's purpose. A starting point you edit — not a wall of generic text.

Home · Selected workTone: assured · specific

Three projects, three difficult sites.

A hillside house on a flood-prone plot. A workshop squeezed between two listed facades. A mixed-use block where the brief changed twice. Each one finished on a budget the client could live with.

RegenerateShorterEdit
06 — Website blueprint

Combine the outputs into a complete website planning document.

Strategy, sitemap, page structures, content and notes for design and development — assembled into one document the whole team can build from.

01Strategy
02Sitemap
03Page structures
04Content
05Design notes
06Dev notes

From brief to blueprint

See the transformation.

Hover or focus an item in the blueprint to see where in the brief it came from.

Illustrative example · fictional client
Before · client emailUnstructured

Hi — so we run a small architecture studio, 14 of us, mostly residential plus a few commercial jobs. Our site is from 2016 and honestly embarrassing. We mostly get work from private clients and a couple of developers, and we want them to understand how we work before they call. Needs a proper projects section, something about the team, and please nothing that looks like every other architect's site. Launch before spring if possible. Attached a few sites we like.

After · website blueprintStructured
  • BusinessArchitecture studio · 14 people
  • ServicesResidential; small commercial
  • AudiencePrivate clients; small developers
  • Primary goalMake the approach legible before first contact
  • SitemapProjects index + detail template as a core section
  • SitemapStudio page: people and places
  • Design directionAvoid genre conventions; calm, detail-led
  • Production noteLaunch target: before spring

AI, applied carefully

Intelligence where the planning happens.

WebArt AI is designed to use AI reasoning to interpret business context, identify relationships between pieces of information, and turn that context into structured website decisions. The AI does the reading and the first draft of the thinking; the professional stays in charge of the judgement.

  1. 01

    Interpret context

    Read a brief as a business situation, not a bag of keywords — including what is implied, and what is missing.

  2. 02

    Identify relationships

    Connect audience to goals, goals to pages, pages to sections, so each decision can be traced to its reason.

  3. 03

    Produce structured decisions

    Output a plan in a consistent structure that a human can review, edit and build from.

Product system

How the pieces connect.

  1. A designer, developer or small agency with a client brief in hand.

    01 User

    A designer, developer or small agency with a client brief in hand.

  2. The workspace where the project lives and the workflow runs.

    02 WebArt AI

    The workspace where the project lives and the workflow runs.

  3. The brief, documents and links — organized, with gaps made visible.

    03 Business context

    The brief, documents and links — organized, with gaps made visible.

  4. Interprets the context and proposes structured decisions.

    04 AI reasoning

    Interprets the context and proposes structured decisions.

  5. Analysis, strategy, sitemap, page plans and content — reviewed and edited by the user.

    05 Structured output

    Analysis, strategy, sitemap, page plans and content — reviewed and edited by the user.

  6. One build-ready document for design and development.

    06 Website blueprint

    One build-ready document for design and development.

What comes next

From blueprint to production.

Only the first column exists as work in progress. The rest is direction, not promise.

NowMVP · in development
  • Strategy
  • Sitemap
  • Page planning
  • Content
  • Blueprint

Being built. Not yet publicly available.

NextPlanned
  • Design workflows
  • Production workflows
  • Integrations

Direction we intend to explore after the MVP. Scope will change.

LaterVision
  • End-to-end website production

The long-term idea: understanding → strategy → blueprint → design → development → launch, connected.

Build from a better blueprint.

Talk to Web Art Technology