Transparent pricing.
No surprises.

What tech stack do you use?

React, Next.js, Swift/SwiftUI for iOS, Kotlin/Jetpack Compose for Android, Node.js, and PostgreSQL. I pick the right tools for the project, not the other way around.

Do I own the code?

Yes. All custom code, designs, assets, and work created specifically for your project transfers to you upon final payment. Full ownership, no licensing fees, no royalties. The only things I retain rights to are my pre-existing internal tools, reusable templates, and generic component libraries that I may use across multiple projects. Think of it like a contractor who owns their own power tools but hands you the finished house.

What are my IP rights exactly?

Upon final payment, you receive a complete, irrevocable transfer of all intellectual property created for your project: source code, UI/UX designs, custom graphics, copy, and documentation. You're free to modify, resell, or redistribute as you see fit. I retain a license to reuse generic, non-client-specific patterns, templates, and boilerplate code that form part of my development toolkit. Your unique business logic, branding, and custom features are 100% yours. Open-source libraries (e.g. React, Next.js) stay under their own licenses, which is standard.

What's the difference between template and custom?

Template sites use a proven, polished layout customized with your branding and content. Custom sites are designed from scratch, unique to you. Both are high quality, but custom gives you a one-of-a-kind result.

Can I request changes after launch?

Each project includes revision rounds during development. After launch, you get 30 days of free support: bug fixes, minor adjustments, and questions. After that, ongoing maintenance and feature work is available at $450/mo for a support retainer.

How do you handle security and my users' data?

Security is part of the build, not a line item. Here is the approach behind every product I've shipped so far, and the starting point for yours. Connections to third-party services use their official sign-in flows, so passwords are never seen or stored. Tokens and credentials are encrypted and kept server-side, out of reach of the browser. Database rules deny client access to sensitive records by default. Data collection stays limited to what a shipped feature actually needs. A recent example: the Tesla voice product never sees a password, never collects location or trip history, and keeps its command-signing key in an isolated service that holds no user data. If your project calls for something different, like an existing system I'm inheriting, we'll talk through the tradeoffs before any work starts.

Do you offer NDAs?

Yes. I'm happy to sign a mutual NDA before we discuss any details. Your idea is yours. I take confidentiality seriously. Just ask and I'll send one over before our first conversation.

How do payments work?

50% upfront to begin, 50% on delivery. Fixed price agreed before any work starts. No hourly billing, no surprises. For projects over $10,000, milestone billing is available: 40% to begin, 30% at the midpoint demo, 30% on delivery.

Why does Android require beta testing?

Google Play requires a structured beta period before production deployment. We coordinate 15 to 20 beta testers for about a month to catch bugs, gather feedback, and ensure a smooth launch. This is built into the Android timeline. No surprises.

Can you speed up the timeline?

Yes. Acceleration is available for most projects. The cost depends on how much faster you need it and the project complexity. Email me and we'll work it out.

Do you work with existing apps or only new ones?

I focus on new builds. Starting from scratch means I control the architecture, code quality, and timeline from day one. You're involved every step, and the foundation is built right from the start.

What if I have an idea but don't know the scope?

That's normal. Send me a message and we'll scope it together. No commitment until we agree on a plan and price.