There are two ways to work with us. We bill hourly at $30 an hour, or we work milestone by milestone. You pick the one that suits the project. We have priced freelance work for more than nine years, across 525 delivered orders rated 4.9 from 343 reviews on Fiverr and 5.0 from 156 on Freelancer. Check both yourself on our reviews page rather than take our word for the number.
Hourly, at $30 an hour
Hourly suits ongoing work, maintenance, and projects where the scope is open or keeps changing. You pay for the time the work takes, and you see the hours logged. You can change direction without rewriting a scope first.
By milestone
Milestone work suits a project you can describe up front. Each milestone is tied to a deliverable you can look at and accept, like a working login flow or a checkout that takes a real test card. Payment follows acceptance of that piece of work.
For a clearly scoped milestone, we can agree a fixed price for that milestone.
A written scope comes first
For milestone work, the scope comes before the work. We write down what’s being built, feature by feature, plus what’s explicitly left out. If the scope isn’t written yet, a milestone price isn’t either.
The document itself, and how we build it, is covered in how we scope projects. A features list alone doesn’t prevent disputes. A written list of what’s excluded, the things a client would otherwise assume were bundled in, does.
What happens when scope changes
Scope changes mid-project are ordinary and not a problem by themselves. What matters is how they’re handled. A change doesn’t get absorbed into a milestone that’s already underway. It becomes its own line or its own milestone, scoped the way the original work was scoped. On hourly work, a change is simply more logged hours.
The second scoping conversation follows the same process as the first one. There’s no looser standard for something added partway through.
Platforms and ownership
If you prefer the protection of a platform, we run projects through Fiverr, Upwork, or Freelancer escrow. Either way, the repository, the hosting account, and the domain are in your name from day one. You talk to the engineers doing the work. The full sequence a project moves through, from first contact to handover, is on how projects run.
When we say no
Some projects don’t get taken on at all. We turn down work we can’t scope honestly, where the requirements are too undefined to write a real included list and excluded list against, unless hourly work to find the shape of it makes sense. We turn down budgets that would force corner-cutting to hit the number. And where a cheaper answer already exists, an off-the-shelf tool or a template that does the job, we say which one instead of building something custom to replace it.
The size of the project doesn’t decide it. What decides it is whether we can give you an honest answer about the work in front of us. Tell us what you’re building and we’ll tell you whether hourly or milestones fits it better.