Fixed-scope project
A defined project with agreed deliverables, milestones and a clear finish line.
- Discovery and scoping
- Design and build to an agreed specification
- Launch support
- Documentation and handover
Most digital products pass between a design agency, a development shop and a hosting provider. We keep them in one team, from brand and interface design through engineering, infrastructure and the support that follows launch.
01One team
Design decisions affect how a product is built. Build decisions affect how it runs. When one team owns all three, nothing gets lost at the hand-over, because there isn’t one.
You work with the same strategists, designers and engineers from the first workshop to the hundredth release.
Designers and engineers work from the same brief, in the same tools, on the same timeline.
Technical constraints shape the design early, and the design intent survives the build.
The team that built the product is the team that keeps it fast, secure and improving.
02Design
Brand, experience and interface design grounded in what the product has to do, for the business and for the people using it.
Typical deliverables
Identities that hold up across every screen, product and touchpoint.
Positioning, audience and messaging defined before anything is drawn, so the identity has a clear job to do.
Marks, typography, colour and visual language designed as a flexible system rather than a single logo file.
Tokens, components and guidelines that keep brand and product consistent as teams and features grow.
Interfaces designed around real tasks, and tested before they’re built.
User journeys, information architecture and interface design for websites, applications and software.
Responsive layouts, content structure and visual design that make a website easy to use and easy to maintain.
End-to-end design for SaaS and digital products, from first concept through to iterative releases.
Clickable prototypes to test flows, gather feedback and de-risk decisions before development starts.
03Build
Engineering for websites, content platforms, commerce, applications, AI assistants and custom software, on the technology that suits the product, built to be maintained.
Typical deliverables
Fast, accessible websites and stores that your team can run day to day.
Custom, CMS-driven and headless websites, built for speed, accessibility and search visibility.
Shopify, WooCommerce and custom storefronts, with the catalogue, payment and fulfilment integrations behind them.
Any CMS, chosen for the team who will run it. We also move sites between platforms and build custom ones.
WordPress, WooCommerce, Shopify, Webflow, Squarespace, Wix, Framer, Drupal, Joomla, Magento, Craft and Ghost, built as custom themes rather than stock templates.
Sanity, Strapi or Contentful behind a custom frontend, when the same content has to serve a site, an app and partners.
Moving content, media, URLs and redirects between platforms without losing search visibility.
A bespoke editing experience with structured content models, for when no existing platform fits the way you publish.
A walkthrough, a written guide and an editing setup your team can run day to day without us.
New behaviour inside the platform you already use, written to survive its updates.
Custom plugins for features the directory does not cover, written to WordPress coding standards.
Bespoke pricing, shipping, checkout and fulfilment logic for stores with rules of their own.
Private and public apps that extend the storefront, the admin or the checkout.
Chrome and Firefox extensions for internal tools and customer-facing utilities.
Custom modules and connectors for the platforms already running across your business.
Updates, compatibility testing and fixes as the host platform changes around them.
Web and mobile products with real users, real data and real workflows.
Browser-based tools, portals and dashboards with secure accounts, roles and permissions.
Multi-tenant products with subscriptions, onboarding and the admin tooling needed to run them.
iOS and Android apps, cross-platform or native, connected to the same backend as your web product.
Staff dashboards, client portals and admin tools that replace spreadsheets and manual processes.
The systems behind the interface, and the connections between them.
Internal platforms and business tools built around the way your organisation actually works.
Documented, versioned REST APIs that connect products, partners and data.
Payments, CRM, messaging, maps, analytics and other third-party services, connected reliably.
Workflows that remove repetitive manual work, from data syncing to notifications and reporting.
Assistants that answer from your own content, and automation that takes the repetitive work off your team.
Assistants on your site that answer product and service questions, qualify enquiries and hand over to a person when they should.
Bots that take the repeat questions in your support channels and pass everything else to your team with the context attached.
Answers drawn from your documents, catalogue and policies, with sources shown and clear limits on what the assistant will say.
Search, summaries, drafting and classification built into an existing application, behind your own accounts and permissions.
Routing, tagging, extraction and reporting handled automatically, with a person kept in the loop where it matters.
Wired into the CRM, helpdesk, store or database you already run, so answers and actions stay in one place.
04Operate
Hosting, maintenance and ongoing development, so the product stays fast, secure and useful long after launch day.
Typical deliverables
Environments set up properly from day one, and watched after that.
Managed hosting for websites and applications, sized to the product and its traffic.
Cloud environments on AWS and other providers, configured for security, resilience and cost control.
Automated build and release pipelines with staging environments, so updates go live safely.
Uptime, error and performance monitoring, with alerts that reach someone who can act on them.
Launch is the start of a product’s life, not the end of the project.
Core, plugin and dependency updates, backups and routine health checks for live websites.
Framework upgrades, bug fixes and dependency management for applications and software.
Audits and improvements to load times, Core Web Vitals and infrastructure efficiency.
Patching, hardening and access reviews to keep the product and its data protected.
New features and improvements delivered continuously against a prioritised backlog.
A direct line to the engineers who know your product when something needs attention.
05Technology
We aren’t tied to one platform. The right stack depends on what the product needs to do, who will run it and how it needs to grow, so that’s where every recommendation starts.
The stack follows the requirements, audience, content, integrations, budget and the team who will run it day to day.
Readable code, documented decisions and conventions that other developers can pick up without us in the room.
Repositories, hosting and service accounts are set up so your business stays in control of its product.
Open standards and portable platforms, so moving or extending the product never means starting again.
New tools earn their place. We choose mature technology unless something newer clearly serves the product better.
A sample of what we work with, not a fixed menu, the stack is chosen per project.
06Process
Every engagement follows the same four phases. The depth of each one changes with the project; the order doesn’t.
Phase 01
We start with the business, the people using the product and the technical constraints, before any design or technology decisions are made.
Phase 02
We turn the strategy into clear user journeys, visual systems and interfaces, prototyped and tested against real objectives.
Phase 03
We build reliable websites, applications and software on the technology best suited to the product, tested, documented and ready to grow.
Phase 04
We deploy, monitor, maintain and keep improving what we build, so the product gets better after launch, not older.
07Engagement
Choose the model that matches where your product is today. Many projects start with a fixed scope and move to a retainer after launch.
Work runs from a single small website through to a long term product partnership. Tell us the budget you have and we will shape the scope around it.
A defined project with agreed deliverables, milestones and a clear finish line.
Reserved design and engineering time each month for maintenance, improvements and new features.
A long-term design and engineering team working to your product roadmap.
08FAQ
Something not covered here? Ask us directly, we’d rather answer a specific question than guess at it.
Ask a questionYes. We regularly join existing teams, reviewing the codebase, agreeing conventions and working inside your repositories and processes. If we find risks in the current setup, we explain them and propose a plan rather than insisting on a rebuild.
No. WordPress is one of many platforms we work with, alongside WooCommerce, Shopify, Webflow, Squarespace, Wix, Framer, Drupal, Joomla, Magento, Craft and Ghost, as well as headless setups and custom builds in Laravel, Node.js and React frameworks such as Next.js. We recommend a stack based on the product’s requirements, the team who will run it and how it needs to grow, and we migrate sites between platforms when the current one no longer fits.
Our intended position: once a project is paid for, source code, design files and project documentation are handed over to you, and hosting and third-party accounts are set up in your business’s name. Final terms will be confirmed in our client agreement.
After an initial conversation we scope the work: goals, features, integrations, content and risks. Fixed-scope projects receive a detailed estimate and milestone plan. Retainers and partnerships are planned around a monthly allocation of design and engineering time.
Yes. We start with a technical audit covering code quality, hosting, security, performance and dependencies, then agree what to fix first. Once the essentials are stable, most takeovers move onto a maintenance retainer.
Yes. We can host and manage websites and applications for you, or deploy to infrastructure you already own. Either way, we set up backups, monitoring and a documented deployment process.
Yes. Most clients work with us across the full lifecycle, but we also take on design-only and development-only work, including building from designs created by another team.
Yes. We build assistants for websites, support channels and internal teams, grounded in your own content so the answers stay accurate, with clear limits on what the bot will respond to and a hand over to a person when it should. We also add AI features such as search, summaries and classification inside existing products, and connect them to the CRM, helpdesk or store you already run. See AI bots and assistants for the detail.
Tell us what you’re trying to achieve. We’ll recommend the right mix of design, engineering and support, even if that’s a smaller first step.
Start a project info@miranalabs.comA few quick questions, then we come back to you.