Newnessimworks.com
Nessim Works
Services · Practice 04

Web builds and modernizations for organizations running real infrastructure.

Custom WordPress, headless, and full-stack builds — paired with the legacy stack fluency most boutique shops can't credibly offer. We know what's currently shipping in state government and healthcare back offices (ColdFusion, .NET), and we know what's current (Node.js, Next.js, TypeScript). The modernization path between the two is where we work.

Engagement
Phased, 6–20 weeks
CMS depth
WordPress · Joomla · Drupal · Mura · Masa · custom
Languages
TypeScript · PHP · C# · ColdFusion · Node.js
Accessibility
WCAG 2.2 AA built in
What you get

Deliverables, no surprises.

Discovery and architecture

01

Stakeholder interviews, content and code audit where a legacy stack is in play, integration mapping, and a written architecture decision record. You leave discovery knowing what we're building, on what stack, and why.

WordPress or CMS build

02

Production builds on WordPress, Drupal, Joomla, Mura, Masa, or custom. Custom themes and blocks, editor experience configured for the team that will actually use it, accessibility patterns delivered in the build — not retrofitted.

Legacy stack modernization

03

ColdFusion and .NET modernization paths. Strangler-fig migrations where a clean cutover isn't realistic, in-place upgrades where it is. Procurement-readable scope documents, so the modernization can clear an approval cycle without rewrites.

Custom CMS and headless integration

04

Headless WordPress, headless Payload, custom content APIs into Next.js or Node.js front ends. Integration with the systems already running your business (CRM, intake, payment, scheduling, reporting).

Deployment and handoff

05

Staging, QA, accessibility verification, phased rollout, and a runbook the next person to touch the site can actually follow. Optional transition into a maintenance care plan so the build doesn't decay.

How we work

5 phases. Same team start to finish.

  1. 01

    Scope

    Week 1

    Stakeholder interviews, stack and integration review, a walkthrough of what already exists. We end the week with a written scope, a stack recommendation, and a phased estimate.

  2. 02

    Discovery and design

    Weeks 2–4

    IA, content modeling, wireframes through production design. Architecture decision record for the build. Accessibility patterns and editor experience are designed in, not bolted on later.

  3. 03

    Build

    Weeks 5+

    Front-end, back-end, integrations, editor experience. Weekly check-ins with your stakeholder. Source-controlled, reviewable, with the deployment pipeline built alongside the application.

  4. 04

    Deploy

    Final phase

    Staging, QA, accessibility check, performance check, phased rollout. We're on-call through stabilization. Runbook delivered before we step back.

  5. 05

    Iterate and handoff

    Ongoing

    Editor training, content guidelines, post-launch iteration window. Optional transition into a maintenance care plan or an ongoing partnership engagement.

Fit check

Who this is for — and who it isn't.

This works if
  • You're on a legacy stack (ColdFusion, older .NET) and need a credible modernization path, not a rip-and-replace pitch.
  • You're a state agency, healthcare, nonprofit, or association buyer with complex CMS, integration, or compliance requirements.
  • You want one vendor accountable across consulting, build, deployment, and maintenance — not a handoff chain.
  • You need accessibility and compliance built into the build, not added on after launch.
This doesn't if
  • You want a low-budget brochure site — wrong economics on the small end.
  • You want to outsource the whole thing with no engagement on your end — these builds need a stakeholder.
  • You're an agency looking to white-label resell our delivery — that's not our posture.
Engagement

Pick the shape that fits.

Discovery + scope

Stakeholder interviews, stack and integration review, written architecture and scope document. Outputs are usable whether we build it or you take it elsewhere.

Best fit:You need a defensible scope before committing to a full build.

Most engagements

Full build

Discovery through deployment. Custom build on the right stack for the work, accessibility verified, runbook delivered.

Best fit:You have the project funded and need it built right the first time.

Build and ongoing partnership

Full build plus an ongoing partnership engagement — care plan, iteration roadmap, on-call delivery for the year after launch.

Best fit:You want the team that built it to keep owning it.

Pricing is scoped after a discovery call.

FAQ

Questions we hear most.

Do you still work in ColdFusion?

Yes. Our founder is a ColdFusion developer by trade and the firm carries that fluency forward. State agencies, federal subcontractors, and healthcare back offices still run on it, and replatforming everything at once is rarely the right call. We work in-place where that's the right answer and we plan modernization paths where it isn't.

What CMS platforms do you build on?

WordPress is primary for content-heavy sites. We also build on Joomla, Drupal, Mura, Masa, custom CMS, and headless setups against Next.js or Node.js front ends. The right CMS is the one your editors will actually use and your engineers can actually maintain.

Can you take over an existing site?

Yes. We inherit builds regularly — including builds we didn't write and documentation that doesn't exist. The first engagement is usually a discovery and audit pass so the takeover is scoped honestly, then we move into the modernization or maintenance path that fits.

Do you handle migrations?

Yes. Platform migrations (WordPress to WordPress, legacy CMS to WordPress, monolith to headless), content migrations, and stack migrations (ColdFusion or older .NET to modern stacks). We default to phased migrations with rollback rather than big-bang cutovers, because cutovers fail in ways phased migrations don't.

Is accessibility built in?

Yes. Every build ships against WCAG 2.2 AA by default. Accessibility patterns are designed in during the discovery and design phase, verified during deployment, and documented in the handoff runbook. AAA conformance is available on flows that require it.

Discovery first

Talk to us about your engagement.

Discovery calls are free. Scope, timelines, and pricing are quoted after we understand what you’re solving.

Request a discovery call