Software studio
Play Twice is a software studio. We design and build software for clients, and the people who answer your email are the people who write the code.
Services
These are the kinds of work we take on. Each one starts the same way: a one-page scope with what we build, what we leave out, the price and the date.
Products people sign in to and pay for: accounts, billing, dashboards and an admin side for your team. You get a working product on your domain, with the code in your repository.
iOS and Android apps, native or React Native, from the first screen to the store listing. You install a new build every week while we work.
The tool your team runs on instead of a spreadsheet: orders, stock, approvals, reports. We build it around how the team works today.
AI added where it saves someone time: search over your documents, drafted replies, summaries, pulling data out of files. A person checks the output before it goes anywhere.
Marketing sites and online shops that load fast and that your team can edit. Copy, design and build in one pass.
Casual and puzzle games for iOS and Android. We build a playable prototype first, so you judge the feel before paying for content. We make puzzle games of our own too, and test every rule on them first.
How we work
Write to hello@play-twice.com with a few lines about the project. We reply by the next working day, usually with questions.
What we build, what we leave out, the price and the date, on one page. Nothing starts until you agree it.
Each week you get something you can install or open in a browser, with a short note on what changed. Feedback goes by email, so every decision is written down.
We ship to the stores or to your domain, hand over the code and the setup, and stay on for fixes after launch.
# Scope · <your product>## What we build- <feature>- <feature>- <feature>## What we leave out- <feature>, quoted separately## Price fixed, written here## Release a date, written hereChanges get a new page,agreed before the work.$ git push origin main→ lint passed→ typecheck passed→ tests passed→ build ios · android · web→ preview sent to you by email✓ this week’s build is ready, with a note on what changed# Release and handover[x] Submitted to the stores[x] Live on your domain[x] Error monitoring on[x] Repository moved to your account[x] Setup notes and credentials handed over→ We stay on for fixes after launch.Our templates, as we use them. Your project fills in the brackets.
What we build with
The choice goes in the scope before we start, so you know what your product runs on and who can maintain it after us.
What people use
What runs it
What it connects to
Studio
01 · Design and product
The flows, the interface, the words on each screen and the motion between them.
02 · Engineering and releases
Web, mobile and backend code, the AI integrations and the releases, from the first commit to the store page.
There is no account manager. The person who replies to your email is the person writing the code or drawing the screen.
Working in English · Invoicing from the EU
Principles
Anything we ship has to give people a reason to open it again.
Before a release, we play the build cold twice, a day apart, and cut whatever we skipped the second time.
The person who replies to your email is the person writing the code or drawing the screen.
There is no account manager. Every client email gets a written answer from the people building it by the next working day.
Scope, price and date are agreed on paper before work starts, and then we keep them.
Every proposal fits on one page and lists what is out of scope as clearly as what is in.
People decide whether to trust a product in the empty states, the errors and the loading screens.
Those screens are designed and written before release, with the same care as the home screen.
Web apps and SaaS products, iOS and Android apps, internal tools and dashboards, AI features, websites and games. The same people design and build all of it.
Fixed scope, fixed price, agreed on one page before we start. If the scope changes, we write a new page first and you agree it before we do the work.
The date is on the same page as the price. You get a new build every week, so you see where it stands without asking.
Yes. We read the code first and send a one-page scope for the change, the same as for a new build.
Where it saves someone time, using the OpenAI or Anthropic APIs. Answers cite their source, usage has limits, and a person checks the output before it reaches a customer.
We work in writing. You get a written answer from one of us by the next working day, and every decision stays on record for both sides.
You do, once the project is paid. The repository moves to your account and the code is written for the next team to read.
Work with us
Send a few lines about the project: what it is, who it's for and when you need it. Web, mobile, an internal tool or a game, it starts the same way. Include a budget if you have one. The person who would build it replies in writing by the next working day.
You'll hear back by the next working day.