{c.lede}
{c.sections.map(s => (NEC is the oldest independent music conservatory in the United States. The audience sprawls — prospective undergraduates, doctoral candidates, parents of pre-college students, alumni, concertgoers, faculty, press, donors — and each one arrived at the site with a different job to do.
The previous platform treated them as one. Performances were hard to find. The faculty directory was thin. Media assets lived in a dozen places. Mobile was an afterthought. Dozens of academic departments and ensembles had improvised their own subsites over the years. The result was a digital presence that worked for none of its audiences and was painful to maintain.
This was not a visual problem. It was a structural one.
), }, { id: 'approach', label: '02 · What we did', h2: <>02 What we did, body: ( <>We started with stakeholder interviews. Admissions, advancement, communications, academic leadership, the performance office, the faculty. Thirty-plus conversations before anything was designed. The pattern that surfaced was not surprising: people did not disagree about what the site needed to do. They disagreed about which audience was the priority, and nobody had resolved it.
So we resolved it. We mapped user journeys, audited the existing analytics, and inventoried every piece of content the institution produced. From that work we built a content architecture that treated each major audience as a first-class reader — and a governance model that let departments keep their voices without producing twenty inconsistent subsites.
Then we built. A custom CMS designed around rich media, complex academic structure, and a dynamic performance calendar. A design system that holds institutional identity and artistic personality at once. A mobile experience that was designed first, not retrofitted. Integrated events. A redesigned faculty directory. Video, photography, and sound woven throughout the experience rather than bolted on.
We ran this as a multi-phase engagement over several years, not a single six-month sprint. That was deliberate. A rebuild of that scope doesn't survive contact with a real institution unless you iterate with it.
), }, { id: 'outcome', label: '03 · What changed', h2: <>03 What changed, body: ( <>The navigation simplified. Pages got faster. Mobile stopped being a compromise. The events calendar — something the conservatory actually lives by — became something you could use rather than work around. The faculty directory earned the conservatory it represents. Each department kept its voice, and the whole held together.
Held in a platform built to flex with the next 155.
Now findable, filterable, and actually usable on a phone.
"Striking design, seamless navigation, and excellent use of storytelling." — CASE judges
The CASE award is the public version of a quieter result. The people inside NEC who had been fighting the old platform for years could finally do the work the platform was supposed to support.
), }, { id: 'deliver', label: '04 · Deliverables', h2: <>04 Deliverables, body: (Sean Blanchet runs one of New England's established auction houses. The auction industry has a three-hundred-year model; technology has complicated it more than it simplified it. Multi-platform listing, invoicing, inventory tracking, item processing — all manual, all time-consuming, all friction that compounds across every sale.
The problem was not that the tools didn't exist. The problem was that no existing tool understood the specific shape of an auction house's operation. The workflows were too particular, the data too idiosyncratic, and the pace too fast for any off-the-shelf solution to stick.
The question was not whether to invest in technology. The question was whether anyone would bother learning the business well enough to build something that actually fit.
), }, { id: 'approach', label: '02 · What we did', h2: <>02 What we did, body: ( <>We started with the website — a rebuilt digital backbone that worked for buyers, sellers, and staff at once. That first phase forced us to understand the business. What moves through an auction house. How items are sourced, processed, listed, sold, invoiced, and retrieved. How a sale day actually runs.
That understanding is what made the next phases possible. We built multi-platform integration connecting Revere's inventory to Live Auctioneers and other listing platforms — eliminating the manual re-entry that was eating staff time before every sale. We built custom invoicing and payment processing tools designed around how auction transactions actually work, not how a generic payments platform assumes they work.
Then, as AI tools matured and we understood the bottlenecks well enough to be specific, we built proprietary automation for item processing. Description, categorization, workflow routing — work that had required careful human attention for every single lot, now handled by tools built for this operation and no other.
None of this was a single sprint. Five-plus years of compounding — each phase building on the last because the team doing the building never stopped understanding the business it was building for.
), }, { id: 'outcome', label: '03 · What changed', h2: <>03 What changed, body: ( <>Hours of daily staff time freed. Manual processes that used to require careful human attention for every lot — eliminated or automated. The business grew; the digital infrastructure scaled with it rather than becoming the thing holding it back.
Ongoing. Each phase compounds on the last.
Proprietary AI tools handling what used to require manual attention for every lot.
Not adapted from a generic platform. Built around the actual shape of the business.
The competitive advantage is not the technology itself. It is the depth of understanding behind it. No vendor learning Revere from scratch will replicate what five years of working inside the operation produces.
), }, { id: 'deliver', label: '04 · Deliverables', h2: <>04 Deliverables, body: (EdExchange occupies a genuinely unusual position: it sits between the rigor of university-based research and the practical urgency of educators and policymakers who need that research to be usable. That position is valuable. It is also hard to fund.
Leadership came to Quarterdeck with a set of questions they had been living with for a while. What is EdExchange's distinctive contribution in an education research ecosystem that has many well-funded players? What does sustainability actually look like for a platform like this — not in theory, but in the specific? And if the current model has limits, what are the real alternatives?
Sustainability was not a crisis — it was a question, and they wanted a rigorous answer before it became one.
), }, { id: 'approach', label: '02 · What we did', h2: <>02 What we did, body: ( <>We started with the landscape. Stakeholder interviews inside EdExchange and with the broader community it serves. Market and landscape analysis situating EdExchange against peer platforms, adjacent organizations, and the funding patterns that sustain them. Customer discovery with the educators and policymakers who actually use the platform — understanding what they value, what they would pay for, and what they cannot get elsewhere.
From that research we built a clear picture of where EdExchange's integrated ecosystem value actually lived — the specific combination of research quality, curation, and accessibility that no peer organization fully replicated. That clarity was the foundation for everything that followed.
We then modeled multiple strategic paths. Not a single recommended scenario, but a set of viable business models combining philanthropic support, partnership structures, and earned-revenue approaches — each with financial frameworks and organizational implications spelled out specifically enough to be evaluated, not just considered.
), }, { id: 'outcome', label: '03 · What changed', h2: <>03 What changed, body: ( <>The engagement produced something specific: a clearer value proposition, a set of decision-ready strategic options, and the financial modeling to understand what each one would actually require. Leadership left with a foundation for long-term decisions rather than a document that would age out in six months.
The distinctive contribution EdExchange makes — named and positioned against the broader ecosystem.
Not one answer. A range of real options with financial frameworks attached.
Organizational structures matched to each operating model. Built to survive a leadership conversation.
The work gave EdExchange leadership a clearer, more structured foundation for long-term decision-making — and the ability to have a specific conversation with their board and funders about what they are building toward.
), }, { id: 'deliver', label: '04 · Deliverables', h2: <>04 Deliverables, body: (The organization had recently rebranded from the E4 Center to NCARE, reflecting a shift from a single-funder model to a broader consortium approach. The research priorities were genuine — student attendance, teacher workforce, digital learning, postsecondary pathways — and focused on the districts that most of the education research world ignored: small, mid-sized, and rural.
The problem was structural. A good research agenda and a clear commitment to underserved districts is not, by itself, a funding strategy. The existing model had been built around one anchor funder. The consortium model required NCARE to become legible to a different and more diverse set of funders — and it was not yet.
The distinctiveness was real. The question was whether it could be made visible.
), }, { id: 'approach', label: '02 · What we did', h2: <>02 What we did, body: ( <>We started with the landscape. Who else was doing applied education research, and what gaps in the field did NCARE actually fill? The answer was more specific than NCARE had been able to articulate: the combination of research rigor and a genuine commitment to the districts that university-based research rarely reaches is not common. That intersection was the position.
We worked with leadership to make that position legible. A messaging framework that named what NCARE does differently — not in the language of a mission statement, but in the language a program officer at a major foundation reads and recognizes as distinct. Four core research priorities, sharpened and sequenced. A funding strategy built around the new consortium model rather than the old anchor-funder logic.
Then we built the materials that made the strategy usable: funder-ready documents, engagement strategies for target states and audiences, an operating model that reflected where NCARE was trying to go.
NCARE left the engagement with a market position that was specific, a funding strategy designed for the model it was actually running, and materials ready for the funder conversations it needed to have. The research hadn't changed. What changed was that the work around the research could now hold it.
Identity aligned to the consortium model and the expanded mandate.
Sharpened, sequenced, and positioned for funders — not just for researchers.
Built for multi-partner consortium logic rather than single-funder dependence.
The work gave NCARE the language and the materials to have different conversations — with funders, with partners, and internally. That is what a strategy engagement should do.
), }, { id: 'deliver', label: '04 · Deliverables', h2: <>04 Deliverables, body: (Concord Academy is a nationally recognized independent school with a reputation that its digital presence had stopped reflecting. The website had grown organically over years — new sections added as needs arose, old content accumulating, the CMS becoming less manageable with each successive round of updates. The result was a platform that technically existed but operationally struggled.
Content lived in disconnected areas. News, academics, athletics, and alumni archives had each evolved their own structures, and the lack of coherence showed. Event calendars required manual management. Forms were inconsistent. The system worked until it didn't — and the team maintaining it could tell you exactly where the pain points were, because they encountered them daily.
The challenge was not cosmetic. A visual refresh would not have solved it. What Concord needed was a platform rebuilt from the ground up — one that could hold an institution of this complexity and actually be maintained by the people responsible for it.
), }, { id: 'approach', label: '02 · What we did', h2: <>02 What we did, body: ( <>We rebuilt the platform entirely within a modern WordPress architecture — not a visual refresh, but a structural overhaul that preserved the institution's 1,500+ pages of content while replacing the foundation underneath them. The migration covered news, academic departments, athletics, alumni archives, and every other content area the school had built up over years. Nothing was left behind; the question was how to bring it forward in a form that would hold.
New modular templates addressed the full range of content types the school produces. Improved data structures for news, events, and media galleries meant the content could be found and managed consistently, rather than in the ad-hoc formats each section had developed independently. Custom functionality for calendars, giving, and forms was built around how the school actually operated — not adapted from generic plugins that almost fit.
We set up Pantheon-based Dev→Test→Live deployment environments, giving the IT team a reliable and structured path from development to production. Automated backup and update workflows removed the manual overhead that had been absorbing staff time. Performance optimization — caching, image compression, database cleanup — made the platform faster in ways the school's audiences would notice without knowing why.
The engagement closed with technical documentation and hands-on training for the communications and IT teams who would own the platform going forward. The goal was not a handoff that would require constant outside support. It was a platform the school could run.
), }, { id: 'outcome', label: '03 · What changed', h2: <>03 What changed, body: ( <>The platform the school had maintained became something that maintained itself. Routine updates that had required careful navigation of a fragile system became straightforward. The communications team could create content using modular components without needing technical support. The IT team had a structured deployment pipeline instead of a single environment where changes went directly to production.
Every content area — news, academics, athletics, alumni archives — brought forward intact.
Templates built for the full range of content the school produces. Updates the team can make themselves.
A structured deployment pipeline replacing a single fragile environment. IT finally had a real workflow.
The result was a unified, flexible platform that supports day-to-day operations while dramatically reducing the technical overhead the school had been absorbing. What had been a source of operational friction became something Concord could run — and maintain — with confidence.
), }, { id: 'deliver', label: '04 · Deliverables', h2: <>04 Deliverables, body: (The Women's Edge supports the advancement of women leaders across business and the broader community — a membership organization with a growing events calendar, active research programs, and an audience that expects a digital presence commensurate with the organization's reputation. The website had not kept pace.
The underlying WordPress codebase had been built and extended over nearly a decade. It predated PHP 8, which meant it was running on infrastructure the hosting environment was phasing out. Plugins had accumulated without consolidation. Custom post types and taxonomies had been added to solve individual problems without a coherent data model behind them. The team responsible for maintaining the site had inherited a system that required constant workarounds.
The risk was not theoretical. An aging PHP version is a security surface. A fragile plugin stack is a liability that compounds with every WordPress update. The question was not whether to modernize — it was whether to do it in a way that would actually hold.
), }, { id: 'approach', label: '02 · What we did', h2: <>02 What we did, body: ( <>We rebuilt the platform from the ground up — not a visual redesign, but a structural overhaul that brought the codebase into a state where it could be maintained and extended without constant firefighting. That meant rebuilding for PHP 8 and Pantheon compatibility, replacing deprecated plugins with consolidated functionality, and establishing a Composer-based build workflow with version control that gave the team a real development process rather than direct edits to a production environment.
Ten years of legacy content came with us. We migrated the full content archive and restructured the underlying data architecture — refactoring custom post types and taxonomies so the content model actually matched how the organization produces and uses its content. Events, membership resources, research programs: each type got a structure that would serve the organization long-term, not just survive the transition.
We built automated Dev→Test→Live deployment pipelines on Pantheon, replacing the ad-hoc approach that had made changes to the live site feel risky. Caching and CDN optimization brought load speeds up to where they should be for an organization whose audience includes senior business leaders and donors. Full QA testing before launch. Documentation and staff training after.
The relationship didn't end at launch. Ongoing support through quarterly code audits and feature enhancements means the platform continues to improve rather than slowly accumulating the same technical debt that prompted the rebuild in the first place.
), }, { id: 'outcome', label: '03 · What changed', h2: <>03 What changed, body: ( <>The team that had been working around the platform could work with it. Deployments that had felt risky became routine. The content structure that had grown without a plan became something the communications team could navigate and extend. And the organization had a development relationship — not a vendor who delivered something and left — that would keep the platform current.
Full archive brought forward into a restructured data model built for the long term.
A decade of technical debt resolved. Security surface closed. Platform built to stay current.
Code audits and feature enhancements. The platform keeps improving rather than drifting.
The result is a faster, more resilient platform that can evolve with the organization's growing membership, events, and research programs — maintained by a team that knows what they're working with, supported by a partner who stays in the room.
), }, { id: 'deliver', label: '04 · Deliverables', h2: <>04 Deliverables, body: (The Dan Anderson Renewal Center — HBFF's hub for alumni engagement and lifelong recovery support — was at a strategic inflection point. Referral patterns had shifted. The organization had navigated significant staffing transitions. Consumer expectations around virtual and hybrid care had changed, permanently, in ways the field was still absorbing. The historic operating assumptions that had guided this center were no longer reliable.
At the same time, the underlying demand was growing. The need for recovery support beyond acute treatment — peer connection, ongoing programming, family services, sustained engagement — was real and increasing. The challenge was not whether lifelong recovery programming mattered. The challenge was how to deliver it in ways that were financially sustainable, accessible across different models of care, and measurable enough to make the case internally and to funders.
HBFF came to Quarterdeck with four strategic questions that they had not been able to answer from inside the organization: How should lifelong recovery and alumni engagement evolve in a post-COVID, hybrid care environment? What role should in-person, virtual, and digital offerings play going forward? How could renewal programming be financially sustainable while staying true to the mission? And how might these offerings reinforce the foundation's long-term strategic position — rather than functioning as peripheral programs?
), }, { id: 'approach', label: '02 · What we did', h2: <>02 What we did, body: ( <>We led a structured, multi-phase strategy and innovation process to answer HBFF's core questions using evidence — not assumptions.
Internal insight and alignment. We began by interviewing HBFF leadership, clinicians, and program teams to understand how the organization viewed renewal and lifelong recovery support. These conversations highlighted a strong commitment to the mission, identified opportunities to further integrate services and strengthen coordination, and established a clear set of hypotheses to test through external research.
Consumer insight. We conducted qualitative and quantitative research across three groups: alumni engaged in renewal programming, alumni not currently engaged, and individuals in recovery outside the HBFF community. Understanding both engagement and non-engagement was as important as understanding why people participate. This research surfaced clear differences in needs, preferences, recovery capital, and engagement patterns across in-person, virtual, and hybrid models — and confirmed that support needs evolve across stages of recovery.
Market and competitive landscape. We analyzed recovery support models including peer networks, digital tools, retreat programming, and family services. We assessed reimbursement dynamics across private pay, insurance, government, and philanthropy, and broader trends including value-based care, virtual delivery, and the integration of mental health into behavioral health. This clarified where HBFF's strengths — brand trust, clinical credibility, spiritual programming, and family services — create real differentiation, and where new capabilities or partnerships could expand impact.
Financial and operating model design. We worked closely with HBFF leadership to analyze program-level economics across renewal and related offerings, including cost structures, staffing models, and utilization trends. We modeled multiple scenarios to assess evolving demand and referral patterns, and to design funding and operating models that are both mission-aligned and financially sustainable.
Innovation and product strategy. Using a structured, design-based process — including facilitated workshops and advisory input — we worked with HBFF leadership to identify, prioritize, and evaluate new product and program opportunities. This included ideation, concept refinement, and business modeling, with a clear path from pilot to scale.
Alignment and execution planning. We translated the work into a clear strategic direction, a set of prioritized initiatives, and a pilot framework designed for implementation — enabling leadership to move from analysis to action.
), }, { id: 'outcome', label: '03 · What changed', h2: <>03 What changed, body: ( <>HBFF left the engagement with something the organization had not previously had: a market-informed strategy for renewal and lifelong recovery that was grounded in real consumer research, honest about the financial realities, and aligned with the mission rather than in tension with it. The renewal programming that had sometimes been treated as a legacy obligation was repositioned — both strategically and organizationally — as a core component of HBFF's long-term impact and competitive relevance.
Engaged alumni, non-engaged alumni, and people in recovery outside the HBFF ecosystem — including the people not engaging, which mattered most.
From four unresolved strategic questions to a defined path — with product concepts, pilot priorities, and financial models attached.
Operating models designed to work across private pay, insurance, philanthropy, and government — without trading mission for margin.
The harder outcome — the one that matters more than any deliverable — was the internal alignment the process produced. Leadership teams at legacy institutions often know what needs to change. What they need is the external rigor and structured process to resolve the questions that internal consensus alone cannot answer. That is what this engagement was designed to produce, and what it did.
), }, { id: 'deliver', label: '04 · Deliverables', h2: <>04 Deliverables, body: (KVC's portfolio spans coastal homes, traditional New England architecture, contemporary renovations, and custom detail work that doesn't survive compression or slow load times. For a firm whose reputation is built on craft, a website that loads slowly, breaks on mobile, or compromises the photography is not a minor problem — it's a direct misrepresentation of the work.
The graphic design and visual direction for the site came from another firm. Quarterdeck's role was technical: take the design system and bring it to life in a way that performed at the level the work demanded. That meant image optimization without visible quality loss, responsive behavior across every viewport, and a platform stable enough that the team could maintain and update it without outside help for every change.
), }, { id: 'approach', label: '02 · What we did', h2: <>02 What we did, body: ( <>We built the site to handle the visual weight of high-resolution photography without sacrificing speed. Image optimization, lazy loading, caching, and CDN configuration were not afterthoughts — they were architectural decisions made before a line of code was written. The result is a site that loads quickly even on the pages that lead with full-bleed photography of finished interiors and architectural details.
Responsive behavior was built carefully rather than adapted after the fact. KVC's audience includes clients and referral partners who encounter the site on every kind of device — a portfolio that breaks on a phone or displays poorly on a tablet is a missed opportunity at the moments that matter. Every layout was tested across viewports as a first-class concern, not a final QA checkbox.
The CMS was configured to give the KVC team genuine control over their portfolio. Adding new projects, updating project categories, and managing content doesn't require a developer for routine changes — which matters for a firm whose portfolio grows with every project they complete.
), }, { id: 'outcome', label: '03 · What changed', h2: <>03 What changed, body: ( <>A site that represents the quality of the work it's showing. Photography that loads fast and renders well. A portfolio the team can maintain and extend themselves. Consistent behavior across the devices their clients actually use.
Optimized delivery so high-resolution photography doesn't come at the cost of load time.
Responsive behavior designed first, not retrofitted. Works the way it should on phone, tablet, and desktop.
Portfolio updates, new projects, content changes — all manageable without a developer in the room.
{c.lede}
{c.sections.map(s => ({n.body}