Idea to installable MVP in 10 to 15 working days
Start with one useful workflow and builds your testers can install. Choose the scope below; we confirm a start date once the required content and account access are ready. Public store review is separate.
Fixed price, fixed window
We agree the scope, price, and start date before work begins. Extra work needs a separate written agreement.
Built and reviewed by me
I use AI tools for repetitive implementation work and remain responsible for the design, code review, testing, and release.
Access from the start
The repository and service accounts are in your organization from the start. Ownership of custom deliverables transfers after full payment, as set out in the project agreement.
Pick the sprint that fits
Both sprints cover one focused app workflow. Choose the health-tech version when the pilot needs additional access controls, audit logging, and the required vendor arrangements. Legal and organizational compliance remain a separate responsibility.
MVP Sprint
One core workflow, up to six screens, and iPhone and Android builds for invited testers.
In scope
- One user role, one core workflow, and up to six core screens
- Flutter app for iOS + Android from one shared codebase
- Supabase backend (Postgres + auth + storage)
- One sign-in method: email magic link, Google, or Apple
- One paid integration: Stripe, Twilio, or SendGrid (pick one)
- TestFlight build and Play Internal track submission
- Linear board access for the duration of the sprint
- Recorded working-software demos on days 5 and 10
- Repository in your GitHub organization from day one
Not included
- Custom design system or brand identity work
- Additional user roles, core workflows, or admin dashboard
- Native iOS or Android platform modules (Swift / Kotlin)
- Additional health-data controls (see the health-tech tier below)
- App Store / Play marketing assets, screenshots, copy
- Production-grade observability, on-call, or SLAs
Health-tech MVP Sprint
The same focused app build, with additional access controls, audit logging, and a documented setup for your legal and security reviewers.
In scope
- Everything in the MVP Sprint
- Configuration of your eligible Supabase plan after required BAA arrangements
- AWS account hardening (encryption-at-rest on S3, IAM least-privilege baseline)
- Audit-log schema and Postgres Row Level Security policies
- Inventory of services in the data path (Supabase, AWS, your auth provider) — a list, not legal advice
- Technical handover doc: what was configured, exact AWS / Supabase resources, and the open technical items your security counsel should review
Not included
- Any compliance attestation, certification, or legal sign-off
- Compliance memos, gap analyses, or risk assessments — those belong with your counsel or a HIPAA consultant
- Signing or negotiating BAAs with your vendors on your behalf
- Third-party HIPAA audit
- SOC 2 Type 1 or Type 2
- Penetration test (I can recommend a vendor)
- Full HITRUST or ISO 27001 program
Payment schedule
Two invoices on a 50 / 50 split. The final half is tied to installable builds and handover you can verify.
- 1
50% on kickoff
Triggers repo creation, Linear board access, and the first working-software demo on the calendar.
- 2
50% on TestFlight + Play Internal handover
Final invoice clears when you have working builds in TestFlight and Play Internal, plus the agreed handover documentation.
What if scope changes?
If you request something outside the agreed scope, I will tell you within one business day whether we can swap an equal-size item or quote it as follow-up work.
Equal-size swaps are free before implementation of the affected item begins. Once it is in progress, changing it means removing equivalent work or quoting a follow-up.
A second integration, additional design work, or a new platform target receives its own quote and timeline.
Frequently asked questions
How can you offer this price?+
The scope is small: one user role, one core workflow, up to six screens, one integration, and one sign-in method. You work directly with me. I use AI tools where they help with implementation, and personally review and test the work.
What if my idea does not fit the scope?+
I can quote a separate project. A custom design system, native platform modules, or additional workflows need their own scope and timeline. We can work that out on the introductory call.
Do I own the code?+
You have access to the repository and service accounts in your organization from the start. Ownership of the custom code and deliverables transfers after full payment, unless our written agreement says otherwise. Third-party software keeps its own licence terms. There is no proprietary HLT3 platform licence.
What happens after the sprint ends?+
You have a TestFlight build, a Play Internal build, the repo, and the infrastructure. You can keep building in-house, scope a follow-up sprint, or pause to gather user feedback. There is no auto-renewing engagement.
Does the health-tech sprint certify compliance?+
No. The sprint implements the listed technical controls and documents the setup. Your legal and compliance specialists review the vendor arrangements, policies, risks, and intended use. Certification, BAA negotiations, and an ongoing compliance program are not included.
Book a 20-minute intro
We will discuss your idea, check whether either sprint fits, and agree on a useful next step. A rough description is enough.
You can also email contact@hlt3.studio with a few sentences about your project.