Question 1

No calls at all? How does that work?

Accepted Answer

Everything happens in writing: brief, scope, daily updates, revisions. You always know the status without booking a meeting. If your project needs weekly calls, I'm not the right fit — and it's better we both know that now.

Question 2

Is post-launch support included?

Accepted Answer

A 30-day warranty is included: if something I built breaks, I fix it free. Day-to-day content edits you'll handle yourself — the handover doc covers it, and the CMS makes it simple. For ongoing work (new pages, updates, improvements) I offer a monthly retainer — we scope it after launch.

Question 3

What do you need from me to start?

Accepted Answer

A completed project brief, your brand assets (logo, fonts, colors), all copy and images for the site, and any design references or examples you like. If you don't have content ready, we should talk about that before starting — it's the single biggest bottleneck in any project.

Question 4

How does payment work?

Accepted Answer

Payments are split by stage, tied to the same sign-offs you approve. On Upwork it runs through escrow milestones. For direct clients: a deposit upfront, the rest as each stage is approved. No full payment before work starts, and nothing due for a stage until you've signed off on it.

Question 5

I already have a Figma design. Can you just build it?

Accepted Answer

Yes, for full site builds where the design is final. I skip the design phase and build from your file, which usually means a lower price and a faster launch than a full project. It runs the same way as everything else: a written scope doc with a fixed price and date, daily updates, staged approvals.

I don't take one-page or quick-turnaround markup jobs — for those, a specialist who works hourly will serve you better.

Question 6

Can the site integrate with tools like HubSpot, Mailchimp, or Stripe?

Accepted Answer

Yes. Common integrations I set up: HubSpot, Mailchimp, Stripe, Google Analytics, and others, either natively or through automation platforms like Zapier and Make. Tell me what you need in the brief and I'll confirm whether it's straightforward or needs custom work.

Question 7

What platform is the site built on? Will I need you for every change?

Accepted Answer

Depends on the project. For sites your team will edit often, I use Webflow — you get a visual editor to change text, images, and posts without touching code or needing me. For landing pages and content sites where speed and low running cost matter more, I use a code-based stack. Either way you get a handover doc, so day-to-day edits are yours.

Question 8

Do I have to pay a monthly fee to keep the site online?

Accepted Answer

It depends on the stack, and I'll tell you which one fits before we start.

Code-based build: no platform subscription. You pay only for your domain (about $12/year) and any third-party tools you choose. Hosting is free or close to it.

Webflow build: a monthly plan of about $25–40, billed to your own account. In return your team gets a visual editor to update the site without a developer.

Neither is better by default — it's a trade-off between running cost and how easily you edit things yourself. I'll lay out the exact numbers for your project up front.

Question 9

I've seen sites offered in 2–3 days for a third of the price. Why does yours take four weeks?

Accepted Answer

Those are template builds: generated layout, your text dropped in, live in days. For some projects that's genuinely enough. What I do is different work: structure built around your buyer, custom design, a CMS your team can run, and performance that holds up. The four weeks include your feedback and staged approvals — so what launches is what you signed off, not what the generator produced.

selected work

testimonials

how it works

scoping

build

approvals

revisions

launch

packages

faq

start this week, launch in four

yourb2bwebsitefixed pricefixed deadline