Question 1

How long does a typical build take?

Accepted Answer

Most builds run six to twelve weeks from kickoff to launch. Sprints are two weeks. We will give you a date in the proposal and tell you immediately if it slips.

Question 2

Do we own the code?

Accepted Answer

Yes, entirely. Source, infrastructure accounts and documentation transfer to you at handover. There is no proprietary layer you have to keep licensing.

Question 3

What does "operate" actually include?

Accepted Answer

Hosting, monitoring, security updates, backups with tested restores, content and SEO work, and a monthly report with the numbers that matter. Cancel any time with 30 days notice.

Question 4

Can you take over an existing site?

Accepted Answer

Often, yes. We start with a two-week audit so both sides know what we are inheriting before anyone commits to a longer engagement.

Question 5

How do payments work?

Accepted Answer

Fifty percent to book the slot, fifty on launch. Operating agreements are monthly in advance. No hourly billing, no surprise invoices.

Question 6

Do you sell the assets in your portfolio?

Accepted Answer

Some of them. Anything marked "for sale" is genuinely available. The metrics on the page are the real ones, and we will give you read-only analytics access before you commit.

Question 7

What if we want to bring it in-house later?

Accepted Answer

Good. That is what the runbook is for. We have done same-week handovers and we do not make them painful.

Question 8

Which stack do you use?

Accepted Answer

Whatever your team can hire for. In practice that is usually Node, Postgres or SQLite, and plain server-rendered HTML with islands of interactivity where they earn their place.

Help desk

Open a ticket