Process
Fast, because nothing is a surprise
Speed does not come from cutting corners. It comes from deciding early: we agree on the screens before code exists, and from then on you hold a working build in your hand every week.
How we work
Fast, and you see every step
Speed without surprises comes from one rule: you approve the design before we write code, and you hold a working build every week after that.
- Nothing is coded without your sign-off
- A build on your phone every week
- Fixed price per stage
-
01 · Day 1
A brief instead of a call
You fill in a short brief, we ask what is left in writing. The goal, the audience and the one thing the app must do well end up on a single page you can forward to anyone.
- One-page brief
- List of open questions
-
02 · Within 24 hours
Estimate with a fixed price per stage
Scope, timeline and a fixed price for each stage instead of an hourly meter. You know what the prototype costs before you decide on the rest.
- Scope and timeline
- Fixed price per stage
-
03 · About a week You approve here
Clickable prototype you approve
Flows, then a clickable Figma prototype you tap through on your own phone. Comments go right on the screens. Nothing is coded until you say yes.
- Clickable prototype
- Design system
- Your sign-off
-
04 · Weekly
Build in short sprints
Every week you get the working app on your phone (TestFlight on iPhone, an APK on Android, a link for Mini Apps) and a short video of what changed.
- A build every week
- Video demo
- Transparent board
-
05 · Launch
Store release and analytics
Listings, screenshots, review and release. Crash reporting and product analytics are in from day one, so the first users already teach us something.
- App Store and Google Play
- Analytics and crash reports
-
06 · After launch
Support and growth
New OS versions, A/B tests, features the numbers ask for. The code and all accounts stay yours, so you can take them to any team at any time.
- Support plan
- Growth roadmap
Four rules that keep it fast
-
Design approval before code
Every screen is approved in a clickable prototype. Changing a Figma frame costs minutes; changing shipped code costs days.
-
A working version every week
TestFlight, an APK or a Mini App link: you see real progress on your own phone, not a status report.
-
A fixed price per stage
No hourly meter. You approve one stage at a time and always know what the next one costs.
-
Everything is yours
Repositories, developer accounts and servers are registered to you from day one.
Typical timelines
Exact timing comes with the estimate, once we have read your brief.
- Clickable prototype
- about 1 week
- Telegram bot, first version
- from a few days
- Telegram Mini App MVP
- 2-6 weeks
- Mobile app MVP, one platform
- 4-8 weeks
- Second platform on a shared core
- a fraction of the first
What you get access to
- Figma fileThe prototype, the design system and every comment.
- Test buildsTestFlight, Google Play internal testing or a direct APK.
- Task boardWhat is done, what is next, what is waiting for you.
- A shared chatDirect line to the people who design and build.
FAQ
About the process
What if I want to change something mid-project?
Small changes fit into the weekly rhythm. Bigger ones get a short estimate first, so you decide with numbers in front of you.
How involved do I need to be?
About an hour a week: a look at the working version and a round of comments in the chat. The most important moment is the prototype review, where your input shapes everything that follows.
Do you sign an NDA?
Yes, if you need one, before you share the details.
Tell us about your app
No calls: fill in a short brief, and within 24 hours you get an estimate with a fixed price for each stage.