Custom software studio

Briefs go in.
Working software goes live.

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.

Kickoff in 2 weeksFixed-scope sprintsYou own the code
What we do

Six things, done properly.

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.

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

Mobile & games

Cross-platform apps and casual games from first sketch to store listing — including the parts nobody enjoys: build pipelines, review notes, live-ops config.

  • Flutter
  • React Native
  • Unity
  • Store release

AI where it pays

Retrieval, extraction, agents and copilots wired into real workflows — with evals, cost ceilings and a fallback for the day the model is wrong.

  • RAG
  • Agents
  • Evals
  • Guardrails

Product & UX design

Flows, prototypes and a design system your engineers can actually build from. Design happens one sprint ahead of code, never in a separate universe.

  • Figma
  • Prototypes
  • Design system

Rescue & takeover

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.

  • Audit
  • Refactor
  • Handover docs

Embedded engineers

Senior developers inside your team, your board, your standups — for the quarter you need extra hands without another year of headcount.

  • Monthly
  • Your process
  • Your repo
The run of show

How a project actually goes.

Five stages, in this order, every time. You see working software from week three — not a status deck.

ACT 01

Scoping call

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 in
ACT 02

Shaped proposal

A 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 days
ACT 03

Design sprint

Key flows drawn and prototyped before a line of production code. We test the hard screen first, not the login page.

1–2 weeks
ACT 04

Build sprints

Two-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, typical
ACT 05

Launch & handover

Production release, monitoring, runbook and a recorded walkthrough of the codebase. Repos transfer to you — we keep no hostage keys.

Then optional monthly support
Selected work

Shipped, not slideware.

A few recent builds. Details anonymised where clients asked us to.

Mobile game

Onet — a puzzle game with 12 cities

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.

30Levels
52Icons
12Cities
Web application

Operations dashboard for a logistics team

Replaced fourteen spreadsheets with one real-time board: live shipment status, exception alerts and a permissions model the ops lead can change without us.

9 wksTo launch
14Sheets retired
1.4kDaily events
AI integration

Document intake copilot

Extraction pipeline over messy supplier PDFs with a review queue for anything below the confidence threshold. Humans stay in the loop where accuracy matters.

92%Auto-cleared
6 wksBuild
3Model fallbacks
Engagements

Three ways to work with us.

Every option is fixed-price per period, cancellable at the end of any sprint, and includes the source code.

01 · Short

Discovery

from $4,000 / 2 weeks

  • Technical audit or product shaping
  • Clickable prototype of the core flow
  • Architecture and cost estimate
  • Written build plan you can take anywhere
Book discovery
02 · Most chosen

MVP build

from $18,000 / 8 weeks

  • Design plus full-stack build
  • Staging URL from week three
  • Launch, monitoring and runbook
  • 30 days of post-launch fixes included
Start an MVP
03 · Ongoing

Embedded team

from $9,000 / month

  • One to three senior engineers
  • Your repo, your board, your standups
  • Design support on demand
  • Monthly rolling, 30 days notice
Discuss a team
Questions

Before you write in.

How fast can you start?

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.

Do we own the code?

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.

Can you work with our existing team?

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.

What happens when scope changes mid-build?

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.

Which projects do you turn down?

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.

Start here

Tell us what you’re building.

A paragraph is plenty. We reply within two working days with either a scoping call slot or a straight “not us, try these people”.

We read every message ourselves. No newsletter, no CRM sequence.