Question 1

How does pricing work?

Accepted Answer

Every project is scoped and quoted individually — there's no rate card because cookie-cutter prices produce cookie-cutter results. Once I understand what you actually need (via the free audit call), you get a written quote with a fixed total, clear milestones, and no hourly meter running in the background.

Question 2

Will you sign an NDA?

Accepted Answer

Yes, and I prefer it that way. Send yours, or I can provide a mutual one — either way it's signed before we discuss anything sensitive.

Question 3

Who owns the code when the project ends?

Accepted Answer

You do, fully. The finished code goes into your own repository with complete commercial rights. There are no licence fees, no usage clauses, and no dependency on me to keep it running.

Question 4

What if my project isn't a good fit?

Accepted Answer

I'll say so plainly during the audit call. If I know someone better suited, I'll refer you directly. You keep the notes from the call regardless — they're useful whichever way it goes.

Question 5

How long does a typical project take?

Accepted Answer

Most focused builds ship within four to six weeks from the day we agree scope. Larger or more complex work is broken into phases so you're seeing something real early — not waiting months for a big reveal.

Question 6

Can you work with our existing development team?

Accepted Answer

Comfortably. I've stepped into teams mid-project before — adopting existing conventions, joining stand-ups, and reviewing in your pull-request workflow. I won't try to rewrite things that are already working.

Question 7

What technology do you build on?

Accepted Answer

A mature, enterprise-grade backend paired with a modern frontend — the same combination trusted by large institutions, sized and priced for a business that doesn't have an engineering department. The full breakdown is on the Stack page if you want the specifics.

Question 8

Do you handle hosting and infrastructure?

Accepted Answer

Yes. Projects are deployed to reliable cloud infrastructure with automated deployments, monitoring, and backups set up from day one. You won't need a DevOps hire to keep it running.

Question 9

How is security handled?

Accepted Answer

It's built in rather than bolted on — secure authentication, role-based permissions, and encrypted data at rest are defaults, not add-ons. If your industry has specific compliance requirements, we address those during scoping.

Question 10

What kind of support is there after launch?

Accepted Answer

Every project includes a post-launch support period for bug fixes at no extra cost. After that, if you want ongoing help — monitoring, small iterations, or a safety net for incidents — we can set up a simple retainer. The scope and cost depend on what you actually need.

Question 11

Can features be added after the initial launch?

Accepted Answer

Absolutely. The code is yours and it's built to be extended. Whether it's a follow-on sprint or occasional small updates, we can structure it however makes sense for how your business evolves.

Things worth knowingbefore you reach out.