Independent web and systems workNo. I

Digital systems
for real-world operators.

I build websites, dashboards, CMS platforms, and AI workflows. Most of the work begins with someone trying to make a process easier to carry — a sales pipeline, a tool inventory, a public site, a way of writing things down.

Open the Studio Console See the showcase

Builds: Websites · Dashboards · CMS · AI workflows
For: Construction · Wellness · Real estate · Marine · Creative
With: Next.js · TypeScript · Sanity · AI used carefully

§ II

Selected work

Recent projects.

Immersive wellness brand — cold plunge, sauna & contrast therapy, San Francisco.
Vital Ice
Client platform · Substantially built
Problem
A wellness and recovery brand needed a polished public web presence with stronger service storytelling, editable content structure, SEO foundations, and integration readiness.
System built
Next.js site architecture, Sanity CMS direction, service/content structure, SEO-aware pages, booking/link pathways, analytics considerations, and wellness brand storytelling.
Stewardship
Built so the team can update services, posts, and pages without re-engaging a developer for every change.
Skills
- Next.js
- TypeScript
- Sanity CMS
- SEO
- UX Architecture
- Service Pages
- Analytics
- Client Communication
- Responsive Design
Domains
- Wellness
- Recovery
- Small Business Systems
- Client-Facing Web Platforms
Mobile-first construction tool-tracking PWA — Next.js + Supabase.
Field Ledger
Active pilot · Product in development
Problem
Construction teams lose time, money, and trust when shared tools, equipment, and materials are hard to locate or track.
System built
QR-based asset tracking, tool movement workflows, setup checklist, QR label guide, pilot onboarding strategy, dashboard direction, and field-first UX.
Stewardship
Designed for the truck and the jobsite first. Visibility before automation; the dashboard exists to make the work easier to carry forward.
Skills
- Product Design
- Dashboard Design
- QR Workflows
- Construction Operations
- Field UX
- Next.js
- TypeScript
- Documentation
- Pilot Strategy
Domains
- Construction
- Operations
- Stewardship
- Field Teams
Property management, bookkeeping & homebuying — Morgantown, WV.
Tale of Two Rivers
Client project · Real estate website
Built for Frank and Evan.
Problem
Frank and Evan needed a real estate web presence that felt distinct, credible, and more memorable than a generic property or agent website.
System built
A real estate website built around the “Tale of Two Rivers” identity, with place-based visual storytelling, clear brand direction, custom landing page structure, responsive design, and a more atmospheric presentation of the offering.
Stewardship
A real estate site grounded in place, partnership, and clear client-facing storytelling.
Skills
- Web Design
- UX Architecture
- Responsive Design
- Landing Page Strategy
- Visual Storytelling
- Creative Direction
- Brand Positioning
- Copy Direction
- Client Communication
Domains
- Real Estate
- Storytelling
- Visual Identity
- Local Business
- Client-Facing Web Platforms
B2B marketing — marine technology sales engineering & consulting.
Beringia
Website refactor · Marine consulting platform
Problem
A technical marine consulting business needed a clearer public web presence that could communicate credibility, expertise, and environmental context.
System built
Next.js / Sanity direction, marine-themed information architecture, depth-zone visual concept, technical sales positioning, and CMS-ready page structure.
Stewardship
Visual language is grounded in the work — depth zones and environmental cues — not borrowed startup motifs.
Client
“I've worked with a lot of vendors who build what you ask for. Jack built what I meant.”
— Client · beringia-marine.com
Skills
- Next.js
- Sanity CMS
- Information Architecture
- Technical Storytelling
- Environmental Design Language
- Responsive Design
Domains
- Marine Technology
- Environmental Systems
- Consulting
- Technical Sales

See all projects

§ III

Services

Choose the right first system.

Most projects do not need more software at first. They need a clearer first system. These are the common forms that system takes.

I
The Living Brochure
CMS-backed website for a service business.
Best for
Small businesses, consultants, local brands, wellness studios, real estate teams, technical service providers.
Typical first milestone
A focused homepage, service pages, contact path, SEO foundation, and CMS-ready content model.
II
The Operations Ledger
Dashboard for tracking work, assets, tasks, or leads.
Best for
Construction teams, field teams, service businesses, small operations with too many loose spreadsheets.
Typical first milestone
A private dashboard prototype around one core workflow.
III
The AI Clerk
Human-reviewed AI workflow for repetitive admin work.
Best for
Teams with repeated admin tasks, customer inquiries, internal notes, estimates, reports, lead follow-up, or content workflows.
Typical first milestone
One narrow workflow with clear human review before anything is sent, changed, or committed.
IV
The Knowledge House
CMS, documentation, or internal knowledge system.
Best for
Businesses with scattered content, recurring questions, outdated pages, or knowledge trapped in one person’s head.
Typical first milestone
A clean content model, editing workflow, and first organized knowledge area.
V
The Client Portal
Private workspace for files, updates, approvals, or status.
Best for
Construction companies, consultants, service providers, creative studios, real estate teams, and project-based businesses.
Typical first milestone
A secure client view for one project type or customer journey.
VI
The Launch Vessel
Landing page and intake path for a new offer.
Best for
Founders, local businesses, real estate projects, events, workshops, new offers, and early product validation.
Typical first milestone
A landing page, CTA path, intake form, analytics, and follow-up workflow.

§ IV

Studio Console

From a vague brief to a first build path.

Most projects begin with a foggy sentence: “I need a better website,” “I need AI,” “I need a dashboard.” The console walks through a few short questions and returns a first milestone, the inputs it needs, and what should stay under human review.

01 Choose the kind of need
02 Answer practical questions
03 Receive a first build path
04 Send the brief

Open the Studio Console

§ V

Systems Atlas

What the projects share, including the parts that look unrelated.

A list of skills tells you nothing about how the work fits together. The chord below shows which projects share tools, which share a domain, and — the more interesting case — which share a way of thinking even when nothing else lines up.

Project overlap · 11 arcs across 6 projects

The heaviest line on the diagram is between a construction asset tracker and a philosophy project. They share two principles and nothing else. That's the kind of pattern this view is for.

See the full atlas — every shared backbone, every reference →

§ VI

Build process

How I build.

What every project goes through, more or less in this order. Five steps, plain language, no surprises.

01
Discovery
A short call about what is not working. I come back with a one-page brief: the problem in plain words, a first build path, the things that worry me, and what should stay under human review.
You leave with A one-page brief you can take to your team.
02
First milestone
One milestone, written down. What gets built, what gets skipped, who reviews it, what “done” means. I sketch the data model and the page or screen flow before any code is written, so we are looking at the same picture before the work starts.
You leave with A short milestone plan and an outline of the data and pages.
03
Build
A working version on a branch you can preview from day one. I write code I can explain — Next.js, TypeScript, plain CSS — and I keep the structure legible enough that someone else can pick it up later.
You leave with Preview link, updated as the build moves.
04
Handoff
The site or tool, plus what the team needs to keep it running: a README, a content model the editor can actually use, and notes on the places a future change is most likely to land.
You leave with Working system, README, and a maintainer’s map.
05
Maintenance
Optional, paid hourly or in small monthly blocks. The system is built so the team can keep using it without me. If you want me on call for changes, that is a separate arrangement, not a lock-in.
No retainer is required to use what was built.

§ VII

Seventh Agora

A longer project I'm still shaping.

Seventh Agora is a long-term project — essays, principles, and design experiments — about how digital tools shape attention, work, and trust. It isn't a product and it isn't for sale. Some of the choices behind the projects on this site come from it.

Mostly unwritten so far. The site you're reading is the first piece of it that actually exists.

“I've worked with a lot of vendors who build what you ask for. Jack built what I meant.”
— Client, beringia-marine.com

§ VIII

Get in touch

Have a project you'd like to talk about?

Tell me what you're trying to make easier. I'll reply with a small first step — even if that step isn't hiring me.

Start a conversation Try the Studio Console

Or write directly: hello@jackmalzone.com

Digital systemsfor real-world operators.

The Living Brochure

The Operations Ledger

The AI Clerk

The Knowledge House

The Client Portal

The Launch Vessel

A longer project I'm still shaping.

Have a project you'd like to talk about?

Digital systems
for real-world operators.