Fixed-price project
[PLACEHOLDER: starting price — Fixed-price project]
Best for well-defined scope — a set price agreed before work starts.
Three ways to engage. The structure is fixed. The numbers are filled in once you confirm the figures you want published — they are not invented here.
[PLACEHOLDER: starting price — Fixed-price project]
Best for well-defined scope — a set price agreed before work starts.
[PLACEHOLDER: starting price — Hourly]
Best for ongoing feature work or unclear scope — billed against logged hours.
[PLACEHOLDER: starting price — Monthly retainer]
Best for continuous support, maintenance, or a dedicated block of monthly hours.
Split into milestones. You approve a milestone before the next one is treated as due. The price does not move unless the scope does, and scope changes are written down.
Hours are logged against the task, with a short note of what was done. You can stop. There is no minimum buried in the rate beyond what the agreement states.
A monthly block of hours for fixes and small changes. Unused-hour rules are written in the agreement. [PLACEHOLDER: unused retainer hour policy]
The sequence from first call to handover is on how we work. A one-page brief is at project brief template.
Wise, PayPal, Stripe, or a bank transfer in USD. You pick whichever your finance team already uses. Invoices are in USD unless we agree otherwise in writing. We do not ask you to pay into a personal account that is not named on the invoice.
An NDA can be signed before you share a repository or customer data. Every paid engagement has a written scope: what is included, how changes are priced, who owns the code, and how either side stops. Template files are attached once you provide them.[PLACEHOLDER: link to NDA and contract templates]
Send what you want built. You get a fixed quote or a list of the questions that block a fixed quote. Reply within 24 hours on business days.