1. Scope
Goals, content, audience, references, integrations, constraints and success criteria.
PROCESS
A visible path from brief to launch.
Wemaxa structures work into discovery, design, implementation, QA and launch. The exact number of iterations depends on scope, but the project should always have clear decisions and review points.
01DISCOVERY
02DESIGN
03BUILD
04QA
05LAUNCH
PROJECT FLOW
2. Design
Information structure, wireframes or layouts, visual direction and responsive component rules.
3. Build
Front-end, CMS or application logic, integrations, data and production setup.
WHAT THIS SERVICE ACTUALLY INVOLVES
Substance before package names.
This page is explicit about decisions, boundaries and deliverables so a visitor can understand the work before starting a sales conversation.
Discovery removes scope ambiguity
The brief identifies business goals, audience, current site or system, content, integrations, technical constraints and launch expectations. For redesigns, the current site should be audited before useful content or search equity is discarded.
Discovery is also where ownership of content, photography, legal copy, translations and third-party accounts should be clarified. These items commonly delay projects when they are treated as somebody else's future problem.
Design makes decisions visible
The design phase establishes information hierarchy, page architecture, visual direction and responsive behavior. A homepage or key product screen is often the best place to test direction before every page is produced.
Review should focus on decisions that matter: whether the hierarchy is correct, whether the brand feels right, whether the component system can express the content and whether important mobile behavior has been considered.
Build, QA and launch
Implementation turns approved visual rules into code, CMS structures, APIs or application logic. QA then tests the result with actual content rather than the cleanest demo state. Forms, navigation, mobile layouts, roles, error states and deployment settings all need attention appropriate to the project.
Launch includes production configuration, final content checks and handoff. Optional maintenance can begin afterward, but it is not a requirement for owning the completed custom work.
INTERACTIVE PROCESS
Each phase removes a different kind of uncertainty.
Click a phase to see the decision it is meant to resolve.
DISCOVERY
Discovery
Define goals, audience, content, integrations, constraints and the unknowns that could change scope.
SCOPE DETAILS
What we discuss before committing to the build.
These are the practical dimensions that change design, architecture, effort and continuing operation for this service.
DiscoveryRemove scope ambiguity
DesignMake hierarchy and direction visible
BuildTurn approved rules into working software
QATest real states and deployment
LaunchRelease and verify production
SupportOptional continuing operation
WEMAXA WORKING RULEA phase exists to make a decision easier, not to decorate the project schedule.
DELIVERABLES
What can come out of the engagement.
Exact deliverables depend on scope, but these are concrete categories of work rather than vague transformation language.
Scope, architecture notes and content map
Approved visual direction and responsive rules
Working implementation and integrations
Production release, access and handoff
PRACTICAL QUESTIONS
Questions that change the project.
Short answers to the issues that normally affect scope, architecture or handoff.
How many design revisions are included?
That depends on the agreed scope. The useful distinction is between normal refinement inside an approved direction and a full change of direction after implementation has begun. Review points are intended to catch major issues early.
Can development begin before every page is designed?
Often yes, once the system and key patterns are stable. Components, typography, navigation and representative page types can be implemented while later content pages are still being completed, provided the structure is not changing underneath the build.
What happens after launch?
There is a handoff and verification of the production environment. Continuing support can be added if required, but it is optional rather than a condition of owning or using the completed custom work.
Discuss this project with Wemaxa.
Use the project brief or contact the studio directly.