Product size
A landing page, a corporate site or a cabinet — different skeleton, different number of states.
We do not publish “websites from $X” or packages that do not exist. Cost follows scope: pages, flows, integrations, content.
After a short brief we lock the work and the estimate. If the job is not ours, we will say so.
The job first: what “done” looks like, for whom, by when, what already exists. Then the work. Then the number. Not the other way around.
A landing page, a corporate site or a cabinet — different skeleton, different number of states.
A form to email is one thing. CRM, payments, APIs, n8n are another.
If copy and photos are missing, that is extra scope. We do not pass off someone else’s results as yours.
A crushed deadline and parallel revisions cost more than “one extra block on the home page”.
One page around an offer, a form and a launch. Estimate after the offer and traffic channel.
Several sections, SEO structure, leads. Scope follows the site tree and any migration.
One core flow on a production stack. Estimate after the v1 boundary.
n8n, a bot or an AI scenario. Estimate after the process map, not “by node count”.
Because “a website” and “automation” without a job are different projects. A fake floor only creates false expectations.
After the brief — a fixed estimate for the agreed work. If the job changes, we re-estimate instead of silently inflating hours.
Yes, if the job is a simple brochure. We will say so when a studio build is overkill.