What’s included
Start with discovery, user journeys and a build plan that can be reviewed.
The first planning stage turns the brief into concrete delivery work: what needs to be researched, designed, connected, tested and handed over. Deeper technical and commercial details remain visible further down the page.
Define the business job before choosing the stack.
Clarify goals, audiences, current constraints and success measures.
Review competitors, existing systems, content and operational dependencies.
Map the sitemap, user journeys, roles and important conversion paths.
Identify platform, integration, data, migration and ownership decisions.
Turn the brief into screens, components and system boundaries.
Plan responsive layouts, reusable components and content patterns.
Define frontend, backend, database, API and third-party responsibilities.
Document accessibility, browser, performance and security expectations.
Agree review checkpoints, acceptance criteria and handover requirements.
One web engineering service
Choose the right build for the job.
A public-facing website, transactional store and web application solve different problems. We start with users, business rules and operating needs, then scope the simplest suitable platform and the work required to support it.

Business and profile websites
Structured company websites, landing pages, service pages, portfolios and authority profiles with responsive layouts, clear content paths, contact flows and agreed technical SEO foundations.
See business website and profile website details
Web applications and portals
Role-based dashboards, customer or partner portals, workflow tools and SaaS interfaces backed by APIs, permissions, data models and operational workflows.
See custom software and SaaS development
CMS, content and campaign sites
Content-managed sites on WordPress, Webflow, Wix or another fit-for-purpose CMS, planned around the editing model, structured content, page ownership and publishing workflow.
Explore VSN’s WP Essential product
E-commerce and digital commerce
Product catalogs, storefronts, checkout journeys, order workflows, integrations and store handover on Shopify, WooCommerce, OpenCart or an agreed custom architecture.
See e-commerce delivery detailsBuild options
From managed platforms to custom full-stack engineering.
We map the required features and constraints to a platform before recommending a stack. The final proposal lists the chosen platform, included features, third-party services, delivery responsibilities, technical assumptions and client dependencies.
Managed CMS and site builders
WordPress / WP Essential: content-led business sites, custom themes, plugins and commerce through WooCommerce where suitable.
Webflow and Wix: hosted visual CMS/site-builder experiences when editing needs, integrations and platform boundaries fit the brief.
Commerce platforms
Shopify: hosted storefronts, themes, extensions and supported API integrations.
WooCommerce: WordPress-based commerce with configurable extensions.
OpenCart: an open-source store option for catalog and order requirements that fit its extension and hosting model.
Custom PHP applications
Laravel and Symfony can support tailored business applications, APIs, back-office systems and portals. We scope authentication, roles, data handling, operational workflows, integrations, deployment and maintenance separately.
JavaScript and modern application stacks
React, Vue.js and Angular can support interactive interfaces; Next.js and Nuxt.js add framework options around their ecosystems.
Node.js, Express.js and NestJS can be scoped for server-side APIs and services. Selection depends on product complexity, rendering and data needs, team handover, integrations and expected evolution.
Engineering beyond page build
Cover the experience, integrations and operation around the site.
Web delivery can include connected design, content workflows and technical operations. The items below can be combined where the project needs them; each remains visible in the written scope.
UX/UI and responsive design
Map navigation and user journeys, produce page or screen wireframes, define reusable components and build responsive layouts for the agreed devices. Accessibility criteria, languages, browser support and content responsibility are documented before delivery.
Backend services and integration
Design and connect APIs, identity and roles, forms, notifications, search, data models and approved external services. Backend options may include Laravel, Symfony, Django, Ruby on Rails, Node.js with Express or NestJS, and other scoped technologies; integration behavior, error states and vendor costs are identified.
Performance, migration and care
Audit existing structure, content, dependencies, responsive behavior and hosting constraints; plan migration, redirects and backups; test key paths; then scope maintenance, updates, monitoring and feature work around the platform and service window.
AI-enabled web features
Where the problem justifies it, scope functions such as assisted search, content classification, support experiences or recommendations. Data access, human review, failure handling, model/vendor usage and ongoing operating cost must be agreed.
See VSN AI and automation scopeCommerce beyond a theme
Make the shopping journey and store operations work together.
A usable store depends on accurate product information, clear buying steps and reliable handoffs to the people and systems fulfilling orders.

Catalog and product experience
Plan category structure, collections, attributes, variants, search, filters, product details, media and merchandising so shoppers can find and compare what they need. Product facts, pricing, inventory rules and licensed assets require client approval.
Cart, checkout and payments
Configure the agreed purchase path, shipping and tax settings, order notifications and payment-provider integration where supported. Merchant onboarding, provider eligibility, fees, settlement, fraud review and legal product policies remain with the merchant and third parties.
Store connections
Scope integrations with inventory, accounting, CRM, ERP, point of sale, shipping, fulfillment, marketing or analytics tools. Each connection should identify data ownership, sync timing, permissions, error handling, vendor costs and who resolves failures.
Migration and redesign
Plan content and data mapping for products, categories, media, customer records, orders, URLs, metadata and integrations. Staging imports, backups, redirect maps and sample checks reduce migration risk, but cannot remove every third-party or data-quality risk.
Full-stack scope
Define what happens behind each screen.
For custom web applications, the scope can cover responsive frontend screens, server-side logic, database design, APIs, authentication and role permissions, admin workflows, notifications, reporting and connections to approved external services.
Where useful, the architecture may include server-rendered or single-page interfaces, REST or GraphQL APIs, relational or document databases, background jobs, file handling, search, caching and audit logs. These components are selected to meet explicit requirements; they are not added by default.
Security, privacy, accessibility, performance, backups and monitoring need project-specific acceptance criteria. The proposal identifies what VSN implements, what the hosting or platform provider supplies and what the client must own or configure.
How delivery works
A documented path from brief to handover.
Milestones, acceptance checks, client inputs and change handling are agreed before implementation so the build can be reviewed in manageable steps.
Understand the users and job
Review goals, audiences, current site or process, content, competitor patterns, business rules, platform constraints, integrations and success measures. The output is a prioritized brief and open-questions list.
Map pages, flows and architecture
Agree the sitemap or application journeys, key screens, data needs, roles, integrations, technical approach, content responsibilities, delivery phases and acceptance criteria.
Review real increments
Design responsive layouts and reusable components, then implement the scoped pages, CMS structures, features, APIs and connections. Client feedback is scheduled against agreed review checkpoints.
Test the important paths
Check agreed desktop and mobile views, links, forms, permissions, product/cart/checkout paths, supported browsers, content, integrations and error states. Fixes are prioritized against the written scope.
Prepare access and ownership
Confirm domain, hosting or platform access, backups where applicable, redirects, analytics access, environment settings, administrator accounts and rollback responsibilities before a client-approved launch.
Plan what happens after release
Optional maintenance can cover agreed updates, monitoring, issue response, small improvements or feature work. Service windows, response targets, exclusions and recurring fees are defined in a separate support scope.
Quality and ownership
Leave the client able to run what was built.
Each engagement should state who owns the domain, hosting, source repository, CMS or store account, paid apps, API credentials, content and third-party subscriptions. Client-owned accounts and least-privilege access are preferred where practical.
The handover may include administrator access, deployment or publishing steps, agreed technical notes, CMS guidance, known limitations and the list of third-party costs. Source code transfer, licences, app subscriptions, hosting and post-launch support depend on the signed scope and vendor terms.
