Web apps that people can actually use
Dashboards, portals, internal tools and SaaS products, built to last and easy to hand over.
What you get
- A working app in your own repository, with the code, the database schema and a README.
- Sign-in, roles and the checks that stop one user from reading another user's data.
- A deployed preview you can click through while it is being built.
- Handover notes so another developer can pick it up.
Who it is for
- Founders who need a first version they can put in front of users.
- Agencies and small teams that need a tool built, not a template bent.
- Businesses replacing spreadsheets and chat threads with one system.
How it works
- BriefYou describe the problem and who uses the app. I ask what is missing and write it back as a short scope.
- PlanThe scope is split into pieces that can be shown one by one, with the riskiest piece first.
- BuildYou get a preview link as each piece lands, and you can change direction between pieces.
- ShipDeploy, check, hand over the code and the notes.
A small first step
A short discovery: one call, a written scope and a clickable prototype of the hardest screen. Scope and cost are agreed before it starts.
Related work
Questions
Which technology do you use?
Proven, well-supported tools picked for your project, never an experiment. If you already have a codebase, MR Works works in it.
Do I own the code?
Yes. The code lives in your repository and your accounts from the start.
Can you work with my designer?
Yes. I can build from Figma files, or design the screens myself if you have none.
What if the scope changes?
It will. Work is split into small pieces, so a change moves the next piece and not the whole plan.
Do you maintain the app after launch?
Yes, as a separate agreement. It can be a fixed set of hours or fixes only when something breaks.