We prefer well-planned projects to surprises. Our process is designed to eliminate ambiguity before development begins, so that scope, budget, and timeline are clear to everyone—and so we can commit to delivering what we’ve agreed.
Every major project begins with an intensive discovery phase. We review existing systems, analytics, and documentation. We run workshops with stakeholders to understand goals, constraints, and context. We audit technical architecture and integration requirements. We explore information architecture and begin mapping user journeys.
The goal is to move from assumptions to evidence, giving us a shared foundation for everything that follows.
Coming out of discovery, we define detailed requirements and score each for effort. This happens collaboratively and transparently—you’ll see exactly how we’re thinking about the work and what trade-offs exist. Requirements are prioritized against goals and budget, and we agree on what’s in scope for the project.
This is also where we confirm the technical approach: CMS platform, integration strategy, hosting architecture.
We begin with user experience: journey mapping, wireframes, content modeling, information architecture. This work is iterative—we share early, get feedback, and refine. Wireframes are tested against real user needs before we move into visual design.
Visual design translates brand identity into screens and interactions. We develop pattern libraries and design systems that ensure consistency and make future work more efficient. Designs are reviewed and refined before development begins.
Development is organized in sprints, each representing roughly a week of focused work. We build in the open, with regular demos and opportunities for feedback. This isn’t waterfall—we expect to learn things during development that inform the work, and the sprint structure accommodates that.
We handle CMS implementation, front-end and back-end development, and integration work. For Tessitura clients, this includes configuring BlocksOffice or styling TNEW, setting up our proxy service, and building any custom functionality the project requires.
Before handover, we run thorough internal QA across browsers, devices, and assistive technologies. We test against WCAG 2.1 AA as standard. Issues are logged, prioritized, and fixed.
Then comes client review. You’ll have time to test the site against requirements and flag anything that needs attention. We address issues in dedicated remediation sprints before moving toward launch.
We coordinate closely with your team and any third parties to ensure a smooth deployment. In the weeks immediately after launch, a developer familiar with the project monitors servers, error logs, and user feedback, addressing issues quickly as they arise.
No matter how carefully you test, launching to real users in the real world turns up things you hadn’t anticipated. We plan for that.
We aim for long relationships. Most of our clients stay with us for years, and we provide ongoing support that covers bug fixes, small enhancements, and the steady maintenance work a website needs.
We also return for larger engagements as organizations evolve—new features, conversion optimization, design refreshes, responses to changing business needs. The website isn’t finished at launch; it’s a foundation for continued improvement.