services
three kinds of work, one person accountable.
Most engagements are a mix of the three. Scope is agreed in writing before anything is built, and you own the code.
01
internal tools
The thing your team currently runs on a spreadsheet, a shared inbox, and someone's memory. Rebuilt as software with real permissions, an audit trail, and a place for edge cases to live.
typically includes
—admin panels and back offices
—workflow and approval flows
—imports, exports, reporting
—role-based access and audit logs
02
client-facing applications
Portals, dashboards, and products your customers use directly. Built in TypeScript and React, tested, documented, and handed over in a state another developer can pick up.
typically includes
—customer portals and dashboards
—onboarding and account flows
—billing and subscription plumbing
—design implementation from your files
03
infrastructure
The APIs, databases, auth, and deployment underneath — the boring parts that decide whether everything above them keeps working on a Friday afternoon.
typically includes
—api design and integrations
—database schema and migrations
—authentication and permissions
—ci, environments, deployment
how it goes
A call, a written scope, then weekly builds you can click. No status decks.
[ start a project → ]$ solvere --process
01 call — what exists, what hurts
02 written scope and fixed price
03 weekly builds, deployed
04 handover: code, docs, access
05 support if you want it