Thorium

Washington, DC · Web development

Web development grounded in how DC buys

Next.js and TypeScript builds for associations, professional services, and federal-adjacent vendors — with accessibility, analytics, and deployment docs your IT group can live with.

Next.js
Typical stack
WCAG AA
Default target
Preview envs
Per change set
Written SOW
Before deposit

Capabilities

What we build in the District

DC buyers skim fast and compliance teams read slowly. We structure pages, forms, and publishing workflows so both stay satisfied — without bolting on a generic template.

Marketing & org sites

Editor-friendly pages, honest information architecture, and structured data that matches visible copy.

  • Component-based layouts
  • GA4 + consent patterns
  • On-page SEO structure
  • 508-minded markup

Web applications

Authenticated tools for members, staff, or partners — roles, audit logs, and exports that survive scrutiny.

  • Postgres-backed data
  • SSO when required
  • API boundaries documented
  • Background jobs isolated

E-commerce

Checkout flows with taxes, shipping, and refunds spelled out — fewer finance surprises after launch.

  • Stripe / Shopify integrations
  • Webhook monitoring
  • Inventory edge cases named
  • PCI scope discussion up front

CMS & publishing

Sanity, Contentful, or disciplined WordPress — whichever your comms team will actually maintain.

  • Draft → review → publish
  • Role-based editing
  • Media library hygiene
  • Redirect plans on restructure

Migrations & performance

Move off legacy hosts, split monoliths carefully, and set performance budgets with numbers — not Lighthouse vanity chasing.

  • Redirect mapping
  • Zero-downtime cutovers where possible
  • Caching strategy notes
  • Post-launch error budgets
Why DC Businesses Choose Us

Built for the Washington, DC Market

We sit on N Street but ship the same way with distributed teams: Eastern-time standups, written decisions, and staging URLs your security reviewers can hit before DNS moves.

1717 N St NW, Washington DC
(202) 666-9377
hello@thoriumdc.com

Federal-adjacent fluency

Comfortable with Section 508 narratives, privacy policies, and procurement-style change logs.

Stakeholder-aware UX

Homepage, careers, and policy pages treated with the same rigor as the product — because DC visitors judge all three.

Predictable cadence

Fortnightly demos and a public issue list — you always know what is in scope versus parked.

Instrumentation included

Analytics and server logging wired before launch so post-release debates use data, not anecdotes.

Outcomes

How engagements tend to land

Illustrative benchmarks from past work — your mileage depends on offer, traffic, and sales follow-up.

8–12 wk
Typical marketing relaunch
When content arrives on schedule and legal review is bounded
↓ tickets
Post-migration
Structured components and logging usually cut UI defect noise — exact drop depends on legacy state
Handoff
Runbook
Env vars, cron, and on-call expectations documented for your team
AA-first
Accessibility
Automated checks plus manual passes on templates that carry legal risk

How We Work

A transparent, milestone-driven engagement from first call to launch.

1

Scope

Sitemap, integrations, approvers, and risks captured in writing before design spend.

2

Design

Figma for key templates; frozen for build with change requests ticketed.

3

Build

Preview URLs per PR, automated checks, and weekly stakeholder reviews.

4

Launch

DNS checklist, monitoring, and a defined hypercare window in the SOW.

FAQ

Frequently Asked Questions

Straight answers — scoped to what you sell and who has to sign off.

Next step

Tell us what needs to ship

Intro call with a lead engineer or PM — we follow with a written estimate, not a generic deck.

Based at 1717 N Street NW, Washington, DC · hello@thoriumdc.com · (202) 666-9377