What’s been built, and where it runs.
Client websites, each designed, built, secured, deployed and documented end to end.
Two businesses, both running their own sites.
Antioch Counseling & Consulting
LiveA counseling, training, and assessment practice run by a licensed clinical social worker with over three decades in the field, licensed across three states.
She came to us with a site built on a drag-and-drop platform: desktop-only on a phone, an enquiry form that dropped submissions into email, and content she couldn't change without paying someone. We rebuilt it as a real website she owns.
What we actually did
- Built out every part of the business — services, training, resources, fees, downloadable forms — not a brochure page.
- Put her in a visual editor so she changes her own words, photos, and documents without touching code or calling us.
- Built a safety net: if the content system is ever unreachable, the site falls back to its built-in text. It cannot go blank.
- Moved all three enquiry forms behind a server-side endpoint with validation, a field allow-list, an origin check, and a spam trap — and audited the old setup for exposed credentials.
- Rebuilt her enquiry database field for field, with saved views for each request type, what's new this week, and pipeline status.
- Fixed the mobile rendering the old export broke, then verified it on a real iPhone browser — layout, overflow, and scrolling.
- Wrote a two-part handbook — one half plain English for her, one half technical for whoever maintains it next.
- Set up automatic deployment and wrote the domain cutover runbook, including how not to silently break her email in the process.
Level One Game Store
Built, launchingA game store in Pompton Plains, New Jersey, running a weekly events calendar the shop's own team keeps current.
A retail site has a problem a brochure site doesn't: the content changes every week. Events, hours, what's on the front page. If updating it needs a developer, it stops getting updated by the second month. So the shop's team runs all of it.
What we actually did
- Built the events calendar, the rotating home-page banner, and the contact form against a database the team already knew how to use.
- Kept every credential server-side. The pages never talk to the database directly — they call endpoints that hold the key where a visitor can't reach it.
- Made the pages degrade gracefully: if the data layer fails, visitors see built-in content rather than an empty page or an error.
- Wrote an Info page that answers the questions a game store actually gets — hours, house rules, how events run.
- Documented every table, every column, and what must never be renamed — plus a handbook covering common tasks for both the shop team and any future developer.
Websites are what we sell, but they aren't the limit.
Alongside client sites we build our own products: front ends and back ends, relational databases and typed data layers, hardened APIs on servers we administer ourselves, mobile apps taken through store review, subscription billing wired end to end, a game engine, and C++ audio code.
It matters here because the difficult parts of a website are things we have already done: the form that has to reach your CRM, the booking system, the migration that mustn't break your email, the security question nobody asks until launch week.
If your site needs something unusual attached to it, ask.