Custom software
Small systems for real business problems. Intake first. Scope second. Build third.
available by scope
belt.works · Akron, Ohio
Software that earns its keep.
Custom tools, automations, and web systems for businesses with broken manual workflows. Bring the mess. We turn it into narrow scope and build the useful part first.
Services
Useful work. Scoped hard.
Freelance work lives here now: custom software, automation, and web systems for people who need the machine to stop wasting their time.
AI workflows and automation
Agent workflows, internal tools, and boring automation where it saves time or money.
available by scope
Ecommerce funnels
Catalog, upload, proofing, Stripe checkout, and an admin path that does not become a monster.
first client lane
Method
Less mysticism. More receipts.
The point is not to admire the stack. The point is to reduce friction, make the workflow legible, and ship the first thing that proves the rest is worth building.
Intake stays plain.
What has to work, what is currently broken, who uses it, and what failure costs.
Scope gets cut down.
The first useful version ships before the project turns into proposal theater.
Builds leave evidence.
Working software, clean handoff notes, visible status, and fewer mystery boxes.
Proof
Current work.
A few artifacts stay visible because talk is cheap and GitHub is less forgiving than a landing page.
belt.works
The public face of the lab. Research, proof, services, and intake all point through here.
active rebuild
Current priority. Voice is locked. Structure is being rebuilt.
ROOMS
A public, sanitized cockpit for the agent mesh. Status first. Control later.
mock data
Good proof because it makes the work visible.
Towpath
Dispatch, ledger, and handoff layer for work across Jeep, M1, and M4.
working predecessor
Not the product by itself. It matters when it ships visible work.
ShopFloor
Neighborhood repair time bank for tools, practical help, and local know-how.
alpha build
Free to use; sustainability ask lives on belt.works, one page away from the help flow.
Start here
Bring the problem here.
Describe the mess, what has to work, and what failure costs. Then we decide what is worth building first.