Why aren't prices listed?

Because a published number would be wrong for almost everyone. Two projects described with the same sentence can differ by a factor of five once roles, integrations and compliance appear. You get a fixed number after a short scoping conversation, before any work starts.

How do I get a quote?

Send a few sentences about the product, the deadline that matters and a rough budget range. If the shape is clear I quote from that; if not, one call plus a written scope document gets us there.

Do you charge hourly?

No. Hourly billing pays for slowness. Work is either fixed-scope with a fixed price, or a weekly retainer for ongoing delivery.

What are the payment terms?

Fixed-scope projects are split across milestones, starting with a deposit. Retainers are billed weekly or monthly in advance. Everything goes on a written agreement.

What happens if the scope changes mid-build?

The price only moves if you move the scope, and you approve the change before it's built. No surprise line items at the end.

Pricing

No price list. A real number, before you commit.

Every published price range on a developer's site is either so wide it's useless or so narrow it's a bait number. Instead: tell me what you're building, get a written scope and a fixed price you can actually plan around — usually within a day or two of the first message.

Two ways to engage

Fixed scope, fixed price

Best for

MVPs, landing pages, bots — anything with a definable finish line

A written scope document lists what's in, what's cut and the delivery date. The price is agreed before work starts and only changes if you change the scope.

— Scope document before any code
— Milestone-based payments
— Deployment and handover included
— Two weeks of bug-fix cover after launch

Weekly retainer

Best for

Existing products needing continuous delivery

You book a block of my week. Priorities can change every Monday without renegotiating a contract, which is what most funded teams actually need.

— Rolling weekly commitment, cancel with notice
— Direct Telegram thread, no ticket queue
— Deployed previews as work lands
— Written handover notes throughout

What actually drives cost

If you want a cheaper project, these are the levers — not the hourly rate.

Number of user roles

One role is a tool. Three roles with different permissions is a platform — auth, data rules and testing all multiply.

Money movement

Payments, subscriptions, refunds and invoicing add real edge cases: failed charges, proration, tax handling, webhook reliability.

Third-party integrations

Every external API is someone else's uptime and someone else's documentation. Two integrations are fine; seven is a project of its own.

Design ambition

A clean, fast, conventional interface is quick. Custom motion, illustration and bespoke components are worth it sometimes — but they're a line item, not a freebie.

Data and compliance

Handling health, financial or EU personal data brings requirements that change the architecture, not just the copy in a footer.

Deadline pressure

A hard date you cannot move costs more than a flexible one, because it removes the option to sequence work efficiently.

Always included, never a surprise line

— Production deployment, custom domain and SSL.
— Ownership of the code and the infrastructure accounts.
— Responsive behaviour on real phones, not just a desktop demo.
— Basic on-page SEO and analytics before launch.
— Handover documentation written for the next developer.

Pricing questions

Why aren't prices listed?: Because a published number would be wrong for almost everyone. Two projects described with the same sentence can differ by a factor of five once roles, integrations and compliance appear. You get a fixed number after a short scoping conversation, before any work starts.
How do I get a quote?: Send a few sentences about the product, the deadline that matters and a rough budget range. If the shape is clear I quote from that; if not, one call plus a written scope document gets us there.
Do you charge hourly?: No. Hourly billing pays for slowness. Work is either fixed-scope with a fixed price, or a weekly retainer for ongoing delivery.
What are the payment terms?: Fixed-scope projects are split across milestones, starting with a deposit. Retainers are billed weekly or monthly in advance. Everything goes on a written agreement.
What happens if the scope changes mid-build?: The price only moves if you move the scope, and you approve the change before it's built. No surprise line items at the end.

Prefer to just chat?

A few sentences about the project and the deadline is enough to start.

Message on Telegram All contact options

Want a number first? Run the MVP cost calculator or read freelancer vs agency vs in-house.