Web applications
Dashboards, internal tools, marketplaces, customer portals. Typed end to end, tested where it matters, deployed on infrastructure you can afford to run.
- React
- Next.js
- Node
- Postgres
Showmaker is a small senior team that designs, builds and ships web apps, mobile products and AI tools. No account layer, no hand-off theatre — the people who scope your project are the people who write the code.
We stay deliberately narrow. If your problem isn’t on this list we’ll tell you, and point you at someone who does it better.
Dashboards, internal tools, marketplaces, customer portals. Typed end to end, tested where it matters, deployed on infrastructure you can afford to run.
Cross-platform apps and casual games from first sketch to store listing — including the parts nobody enjoys: build pipelines, review notes, live-ops config.
Retrieval, extraction, agents and copilots wired into real workflows — with evals, cost ceilings and a fallback for the day the model is wrong.
Flows, prototypes and a design system your engineers can actually build from. Design happens one sprint ahead of code, never in a separate universe.
Inheriting a codebase from a team that left. We audit, stabilise, document, then ship again — usually with a short written verdict in the first week.
Senior developers inside your team, your board, your standups — for the quarter you need extra hands without another year of headcount.
Five stages, in this order, every time. You see working software from week three — not a status deck.
Forty-five minutes on the problem, the constraint and the deadline. You leave with our honest read on feasibility, even when the answer is “don’t build this”.
Free · within 3 days of you writing inA written scope: what ships, what doesn’t, the architecture, the risks we can see and a fixed price per sprint. One page of plan per two weeks of work.
3–5 daysKey flows drawn and prototyped before a line of production code. We test the hard screen first, not the login page.
1–2 weeksTwo-week cycles, each ending in something deployed to a staging URL you can click. Weekly written update, no meeting required unless you want one.
4–16 weeks, typicalProduction release, monitoring, runbook and a recorded walkthrough of the codebase. Repos transfer to you — we keep no hostage keys.
Then optional monthly supportA few recent builds. Details anonymised where clients asked us to.
Tile-matching game with a themed progression across twelve world cities, 30 hand-tuned levels, a custom 52-icon art set and an offline-first save system.
Replaced fourteen spreadsheets with one real-time board: live shipment status, exception alerts and a permissions model the ops lead can change without us.
Extraction pipeline over messy supplier PDFs with a review queue for anything below the confidence threshold. Humans stay in the loop where accuracy matters.
Every option is fixed-price per period, cancellable at the end of any sprint, and includes the source code.
from $4,000 / 2 weeks
from $18,000 / 8 weeks
from $9,000 / month
Usually two weeks from a signed scope. If you have something genuinely on fire, say so in the first line of your message and we’ll tell you honestly whether we can move sooner.
Yes, entirely. Repositories, infrastructure accounts and design files transfer to you at handover. We keep no licence, no lock-in and no keys you can’t revoke.
Often the best setup. We plug into your repo and process, agree who owns which surface, and review each other’s pull requests like any other colleague.
Scope is fixed inside a sprint and open between sprints. New requests go on a list, get sized, and you decide what enters the next two weeks. Nothing silently expands the invoice.
Anything we can’t staff properly, work with no defined decision-maker, and builds where the plan is to specify everything up front and never look at it again. We’d rather refer you on than start badly.
A paragraph is plenty. We reply within two working days with either a scoping call slot or a straight “not us, try these people”.