A person carrying an idea up paper steps

The tasks you can’t hand off

Now you can: bugs, integrations, SEO, data — any website, any stack. An estimate in hours and a definition of done up front.

Describe your task

A short form, then a reply with a concrete next step

What we take on

From a single bug to the whole technical backlog

Bugs and regressions

Leads that never arriveErrors after releasesUrgent incidents

Technical SEO

URL structure and redirectsIndexing and page speedInternal linking

Integrations

CRM and accounting systemsOnline paymentsData exchange via API

Automation

Bots and notificationsRoutine processesScheduled reports

Data

Import and exportCollection and processingMigrations between systems

Pages and UI

New pages and templatesInterface changesContent edits

Two people building a bridge across a gap

Clear before we start

The scope, the hours, and what done means — before the first line of code, so both sides know where the end is.

Describe your task See an example

A few sentences is enough — we’ll ask about the rest

TICKET #128 · example.comaccepted

The form isn’t sending leads

Leads from the form stopped coming through after a site update. There were no complaints — just silence that took a while to notice.

The form shows a thank-you, but no email arrives Nothing in the CRM since last Thursday Priority: critical — we take it first

accepteddiagnosisfixdone

rate

$25/ hour

An estimate in hours — before we start Billed only for the time actually spent The minimum is one task — no packages required

Any website, any stack

Live, legacy, or still being built — the stack doesn’t matter. The method is the same everywhere: see how it all fits together, find the cause, not the symptom, and check the change broke nothing nearby.

How we work

What gets agreed before we start, and how a task moves from “accepted” to “done”.

See the approach →

Cost and timing

The rate is $25/hour, billed for actual time. Timing comes with the estimate — before we start.

Read the FAQ →

The first step

A description in your own words and one way to reach you — that’s all it takes.

Describe your task →

Common questions

Will you take on a single one-off task?

Yes — that’s the norm, not the exception. Fixing a form or setting up a redirect is reason enough to get in touch. The minimum is one task, and there are no mandatory packages.

Do you work with unfamiliar or legacy code?

Yes. That’s the usual starting point: before estimating, we read the code ourselves and check what it depends on, so the fix doesn’t rest on guesswork. We won’t suggest rewriting your site from scratch.

How does pricing work?

The rate is $25 per hour. Before we start, you get an estimate in hours and a definition of done; you pay only for the time actually spent. If something changes the estimate along the way, you’ll know right away — not from the invoice.

How soon can you start?

We start once we’ve agreed on scope — no long onboarding needed. Timing depends on the task and comes with the estimate in hours — before we start.

What if the project has no tests?

Tests are often missing — that’s normal. We check the change by hand: the main scenario, plus the nearby ones that use the same code. The handover spells out exactly what was checked.

Who releases the change to production?

That’s up to you. We hand over the change with a description and steps for a safe release: ship it yourselves, or we do it — following your process, using your access.

Describe your task

Write it as it comes — text, a list, screenshots. From there, working out the details and the next step is our job.