Ben Dixon
I design and build branded websites, ecommerce experiences, dashboards, and internal tools that help businesses sell better and operate with less friction.
What I Build
The strongest projects connect the customer-facing experience to the systems behind it. That is where I do my best work.
01
Branded business websites and marketing builds that look intentional, load cleanly, and stay editable after launch.
Custom design direction instead of template drag
Content systems clients can actually manage
Responsive builds that feel polished on every screen
02
Stores and discovery flows designed to guide customers, support merchandising, and give the owner real control behind the scenes.
Product discovery beyond flat category pages
Promotions, catalog control, and owner-friendly admin
A storefront built to grow with the business
03
Operational software for owners, staff, and clients when spreadsheets, inbox threads, and patchwork tools are no longer enough.
Admin dashboards shaped around real workflow questions
Portals and tools with role-aware access
Reporting and automation that reduce daily friction
Featured Project
Capture to follow-up
A portfolio-native rebuild of a lead intake, qualification, and routing system designed to turn inbound inquiries into visible operations instead of inbox drift.
This is the kind of project where the website is only the first layer. Structured intake, AI-assisted qualification, routing rules, ops visibility, and human review all live in one connected system.
Active scene: Route. A visible activity feed for every lead handoff.
Scene selector
Tap to expand
Live handoff trail
The strongest proof surface. New leads, AI scoring, outreach, notifications, duplicate checks, and scheduled follow-up all land in one timeline instead of disappearing into separate tools.
This view is curated for the portfolio, but it is designed like a real product surface: specific events, state changes, and accountability signals instead of a static screenshot.
Lead created
08:14 AMNorthfield Dental submitted a new multi-location inquiry.
AI scored
08:15 AMScore 91 / Enterprise fit - staffing + compliance requirements detected.
Email sent
08:16 AMImmediate confirmation email sent to the primary contact.
Slack notified
08:16 AMRouting summary posted in #sales-intake with owner recommendation.
Follow-up scheduled
08:17 AMReminder created for 90-minute follow-up if no owner response is logged.
Duplicate detection
08:17 AMPotential match found against a February RFP draft from the same domain.
Score
91
Enterprise fitRecommended owner: Ben - operations-heavy workflow lead.
Next actions
Confirm duplicate match
Open owner handoff
Check reply status
Faster first response
Every inquiry becomes a scored record with immediate notifications and next-step automation.
Less manual triage
The team sees score, category, duplicate hints, and reasoning before anyone starts a reply thread.
Operational visibility
Managers can track lead flow, ownership, and follow-up health from one surface.
Project type
Internal tool / CRM workflow
Surface area
Capture, qualify, route, operate, review
Stack
Next.js, TypeScript, PostgreSQL, automation
System Breakdown
The homepage stays at system depth: where the information enters, how it gets shaped, how it gets routed, and where operators step in. The deeper implementation narrative lives on the project page.
01
Capture
02
Process
03
Route
04
Operate
05
Review
Homepage depth
This section stays at the system-flow level. It shows how the pieces relate to one another without dropping into file paths, SQL fragments, or implementation notes.
01
The entry point collects structured inquiry data instead of a single unshaped message blob. That makes downstream scoring, filtering, and assignment more reliable from the start.
Result: cleaner handoff data and fewer back-and-forth clarification emails.
02
Incoming records are summarized, categorized, and given an urgency signal. The model helps compress the first read, but the output stays inspectable so staff can see why a lead was treated a certain way.
Result: faster triage without hiding reasoning behind a black box.
03
Assignment logic moves leads toward the right owner while sending the right updates to email, Slack, or a queue. Duplicate hints and follow-up scheduling sit in the same flow so nothing important is scattered.
Result: the system creates momentum the moment a lead lands.
04
Managers need quick reads on intake volume, stalled follow-up, and queue health. The operating surface turns those questions into cards, boards, and counts that can be scanned in seconds.
Result: less guesswork and better day-to-day control.
05
Automation is useful, but operations still need a place to adjust ownership, update status, add notes, and override recommendations. The review surface keeps those controls close to the full lead record.
Result: automation stays accountable to the people running the workflow.
Footnote
Homepage depth stops here. The dedicated project page goes deeper into schema, route structure, and implementation choices.
Work With Me
I am most useful when the project needs both presentation and system thinking: brand, UX, admin control, data, and delivery decisions moving together.
Businesses with real operations behind the site
Teams tired of patching together templates and spreadsheets
Projects where design, admin control, and maintainability all matter
Available for websites, ecommerce, internal tools, consulting, and selected technical roles.
