stages 1–handover · brief: Route the problem. Reveal the system. · convergence confirmed
stage 0
Prediction
The predicted convergence is confident fit. Niswey needs qualified conversations. Prospective clients need credible problem recognition, delivery proof, and a suitable partnership route.
stage 1
Evidence Log
Public evidence is sufficient to begin interpretation. The corpus covers 61 sampled pages from 850 URLs. It also covers 55 reviews, current announcements, competitors, and one live visual audit.
stage 2
Business Context
Niswey has moved from digital-marketing execution toward enterprise HubSpot architecture, proprietary apps, and education specialisation. Its public site separates concrete buyer problems from the larger system story they affect.
stage 2.5
Current State Scenario
Niswey can identify a credible intervention for a concrete HubSpot problem. The buyer must leave that route to understand the wider system change. Local fit and transformation proof remain separate journeys.
stage 3
Intent Alignment
Niswey and problem-defined operators converge on one outcome: the right intervention, understood in system context. The site should answer the immediate problem first, then reveal wider impact where it changes the decision.
stage 4
Competitor
Four competitor sites target broad organisational transformation states. None gives a problem-defined HubSpot operator one continuous buying route. The missing route joins exact fit, system impact, matched proof, and contact.
stage 5
Principles
Six principles turn the confirmed convergence into design constraints. Four govern diagnosis, system context, and proof. Two prevent that depth from slowing buyers who already know what they need.
stage 6a
Experience Architecture
Five independent buying questions become five website responsibilities. Each responsibility preserves the buyer's entry context through fit, proof, and contact. The problem-led route carries Niswey's unowned market opening.
stage 6b
Decision Architecture
The five buying questions require five distinct cognitive modes. Buyers delegate, test continuity, match context, reason about systems, or diagnose an intervention. Each mode produces a concrete buying decision.
stage 6c
Knowledge Architecture
Five buying decisions require five primary knowledge domains. The unowned problem-led route depends on intervention-fit knowledge joined to stack-change knowledge whenever wider consequences affect the decision.
stage 6d
Task Architecture
Five buying questions become five recurring buyer jobs. The selected job is to solve one exact problem without creating another. Every job traces to business philosophy, principles, and required knowledge.
stage 6e
Decision Grid
All five knowledge domains are partly supported by Niswey's public surface. The strongest opening is continuity from an exact problem through fit, system effect, matched proof, and contact. Context loss at contact is verified.
stage 7
Decision Log
Stage 7 remains governed by intervention fit. The structure now covers the complete marketing website. Global and page-level decisions share one model.
stage 7a
Structure
The complete website now has one governed hierarchy. Direct Apps and Services routes remain visible. The homepage creates recognition, page templates explain intervention fit, and every current content family has a target home.
stage 7b
Flows
Five reversible flows now connect the full website structure. Visitors may begin with exploration, a known offer, research, proof, or support. The site preserves their original context and never forces one universal funnel.
stage 8
Design System
The current visual identity has recognisable ingredients but no governed grammar. Three directions are assessed. Operational clarity is recommended, but the visual direction remains a designer decision.
stage 8.1
Modern Visual Exploration
Four modern visual approaches keep Niswey's orange and indigo identity while testing different typography, composition, motion, gradient, and density systems. Taste Skill is used as an execution filter under the Ekam model.
stage 8.2
Kinetic Design Specification
A two-theme design specification for Niswey's Kinetic Intervention visual direction. Both themes preserve the same intervention-fit story, component semantics, typography, layout, and motion behaviour.
stage 8.3
Asset Visual Specification
The frozen production asset system for the Kinetic Intervention direction, using Flowbite Illustrations as the primary explanatory SVG language.
stage 8.4
Homepage Content Structure
An offer-led homepage structure for Niswey. Apps and Services explain what the company does, outcomes show why it matters, proof builds confidence, and a direct calendar booking completes the journey.
stage 9
Template Evaluation
The Niswey website must now be built on the Act3 HubSpot CMS theme. The intent model, IA, flows, and offer-led homepage transfer almost completely. The design system transfers only partly: Act3 has one light rendering, white text on its accent colour, and HubL modules instead of shadcn/ui. A configured child theme with a small custom layer is the recommended route.
stage handover
Intent Alignment Model
The frozen model centres one unowned buying question. A buyer starts with an exact HubSpot problem and sees wider impact before committing. Stage 7 refines intervention fit. Direct Apps and Services paths remain.