Hiring a developer by the hour: when it pays off and what to watch for

A developer by the hour pays off for small, clearly defined tasks such as a website or store change, a bug fix, a new form field or a small integration, and for consultations when you need neither a full project nor a retainer. Watch mainly for who actually does the work, how time is billed, who holds the access and whether anyone reviews the change before it goes live.

Below is a practical guide: when hourly work makes sense, when it does not, and how to write a brief so you pay for as few hours as possible.

When an hourly developer pays off

• Small website and store changes: a new price, text, banner, shipping method or form field.
• Fixing a specific bug: the form does not send, orders do not arrive by email, a page breaks after an update.
• Smaller integrations: exporting orders, connecting a carrier or an invoicing tool.
• Consultation and a second opinion: assessing another company's quote, a code audit, choosing a technology.
• When your vendor does not respond and you need the thing solved now.

When hourly work is not enough

If you need a new information system or app, a "developer by the hour" without a plan ends in a series of patches. In that case it is better to split the job into parts with an hour estimate for each. You still pay only for time worked, but your budget stays under control and you see results as you go. That is how we work in software development with AI.

The hourly rate is not the whole price

When comparing developers, people look at the rate. What matters more is how many hours the task really takes. A cheaper junior may need several times longer than a senior for the same change, and someone still has to review the result.

What to ask	Why it matters
Who does the work?	A senior's rate for a junior's work is the most expensive combination.
How is time rounded?	If every task is billed as a full hour, small changes become needlessly expensive.
Will I get a timesheet?	With hourly work you should know what you are paying for.
When will they start?	A cheap hour in two weeks often costs more than a pricier hour today.
Who reviews the change?	A quick change without review can take down the whole store.

At SaveIT we have one rate: €38 per senior hour, excl. VAT. Thanks to AI assistants we need fewer hours; a small website change takes about 15 minutes as a rough guide. More on the Pricing page.

What to watch for with access

• Do not hand over the main password. Create a separate account for the developer and remove it afterwards.
• Back up before changes. Make sure the site and database are backed up before any edit.
• A test copy pays off for a store, where every bug costs orders.
• The code and access are yours. Changes should live in your repository or on your server, not with the developer.
• An NDA for sensitive data is standard, not an extra.

How to write a brief so it takes as little time as possible

Most hours are not lost on programming but on finding out what exactly is needed. A good brief has:

1. A link to the page with the problem or where the change should go.
2. A screenshot with the spot marked.
3. What happens now and what should happen, in one or two sentences.
4. Access to the admin or server, or a contact for the original vendor.
5. A deadline, if it is genuinely urgent.

Send several small changes together to save the time spent getting oriented in the project.

A senior with AI versus a traditional hourly developer

With hourly work, what matters is how much gets done in an hour. An AI assistant handles the routine, such as finding the right spot in someone else's code, preparing a template change or writing an export, in a fraction of the time. Meanwhile the senior handles what cannot be sped up: whether the change breaks anything, whether it is secure and whether it is the right fix at all. That is why, with us, a senior hour does not turn into an hour of typing but into a finished, reviewed change.

Warning signs

• The developer will not tell you how many hours they expect a task to take, even roughly.
• Changes are made directly on the live site without a backup.
• They ask for your main password instead of their own account.
• After the work they do not tell you what exactly they changed.
• They keep the code and changes to themselves, so you cannot move without them.

When the work repeats

The most expensive hour is the first one on an unfamiliar project, while the developer gets oriented in the code and access. Later changes on the same site go faster. So it pays to:

• Work long term with the same company or person rather than someone new each time.
• Ask for a short note with every change: what changed and where.
• Keep access and passwords in one place on your side, so you can hand them over or revoke them at any time.
• Keep the code in a repository, so every change has a history and can be rolled back.

That way hourly work does not lock you into one vendor, and you pay for fewer and fewer hours.

How it works with us

Send the brief through the form or by email. A senior usually replies the same working day and sends an hour estimate for larger tasks. Routine changes are often done within an hour. AI assistants handle the routine work; a senior reviews every change and verifies it in production. You pay for hours worked, with no retainer. Small changes are handled under Express changes, connections to other systems under Integrations and APIs, and advice or a second opinion under IT consulting.

Got a one-hour task that has been waiting for a week? Send it to us; a few sentences and a link are enough.