How a job runs
Scope first. Then the work.
How Pantas Web takes on a job. Shop speed prices are on the homepage. This page does not list prices.
Scope
We write the scope before we build: which pages, what the bot does, what the booking flow includes, or what the plugin does. That list is what the job is. If a step is still to be validated in a partner's sandbox, the scope says so.
Typical turnaround
A free website mock-up is answered within 48 hours. That timing is stated on the mock-up page. For every other job, the timing is the date we put in the scope. A carrier plugin is not the same length of job as a homepage, so we do not print one studio-wide number here.
Revisions
Changes that sit inside the written scope are part of the job. Shop speed packages include 30 days of fixes after you approve, as the homepage states. Work outside the scope is written down before we start it.
What is automated, and what we review
Some steps can run on their own: converting images to AVIF and WebP, and fetching a PageSpeed result when you use the speed check. We review the words people will read, the scope, the booking rules, and any step that charges someone or books a delivery, before we treat that work as done.
If we can't deliver the scope
If we can't deliver what we scoped, you don't pay for it. On a shop speed job, you already see a private demo and pay only after you approve it.