How do you handle revisions and feedback rounds?
+
Most engagements include three rounds of revisions per major deliverable. I send a Loom walkthrough of every milestone so you can review at your own pace, then we align via a 30-minute call. If we need a fourth round, we discuss whether scope changed — and adjust honestly. No surprise change orders.
Will I work directly with you or with a junior team member?
+
You work with me directly on strategy and major reviews. I have a small senior team that handles execution — design production, development, content writing, ad operations — but I personally review every deliverable before it leaves the studio. No account managers, no offshore handoffs you cannot reach.
What tools and platforms do you use?
+
For design: Figma, Adobe Creative Suite, Spline for 3D. For development: Next.js, WordPress with Elementor or custom themes, Webflow, Shopify. For SEO: Ahrefs, Search Console, Screaming Frog, Surfer. For ads: Google Ads, Meta Business Suite, looker dashboards. For project management: Notion + Slack. I do not gate-keep tools — happy to share access to anything we use on your project.
Do you sign NDAs and protect confidential information?
+
Yes. Mutual NDAs available before any discovery call. All client work stays under tight access controls — only the team members directly working on your project can view files. After project close, I retain working files for two years for support purposes, then archive securely. Nothing goes into public portfolio without written approval.
How do you measure success after launch?
+
We agree on 3-5 KPIs before kickoff — usually a mix of leading indicators (traffic, engagement, click-through, time on site) and lagging ones (form submissions, calls, revenue, qualified pipeline). Monthly reports show movement on all of them, with a plain-English summary of what we shipped, what worked, and what is next. No vanity metrics. No 60-page PDFs you will never read.
Do you offer ongoing support and retainers?
+
Yes. After project delivery, you can move to a monthly retainer (typically 8-20 hours per month) for continuous improvement — A/B testing, content additions, performance optimization, new feature builds. Or pay hourly for ad-hoc work. Most clients stay on retainer for at least six months because compounding work outperforms one-off projects.
What is your typical client engagement length?
+
Project work runs 4-14 weeks depending on scope. Retainer clients average 18 months — most started with one project, saw results, and expanded the relationship. My longest active client is now in year four. I am playing for retention, not transactions.
What happens if we are not happy with the work?
+
First — we will not let that be the outcome. I check in weekly via Loom and Slack so issues surface early, not at the end. If something is not landing, we pause, diagnose, and adjust the approach. Every engagement carries a 14-day satisfaction window post-launch where any reasonable refinement is included at no extra cost.
Why not just custom-code everything?
+
Speed-to-launch and editor accessibility. Elementor lets non-technical teams publish without a developer in the loop. Worth it for many businesses.
No. Done right, Elementor sites hit Lighthouse 85-95. We turn off bloat, lazy-load assets, and use compatible cache stacks like LiteSpeed.
Can I move off Elementor later?
+
Yes — we use clean HTML semantics so content is portable. We have done this migration both ways.
Pro for any client work. The widget library and theme builder save weeks of development time.
Do you do Astra Pro / Kadence too?
+
Yes. We pick the base theme for the project, not the resume.
Why choose Elementor over a general WordPress build?
+
If you want to edit your site yourself after launch without touching code, Elementor is one of the strongest tools for that. I configure Elementor Pro with your brand kit — colours, fonts, global styles — so every page you build stays on-brand automatically. It's particularly well-suited to service businesses and marketing sites where content changes regularly and you don't want to depend on a developer for every update.
Is Elementor slow? I've heard it can hurt page speed.
+
Badly configured Elementor sites can be slow — that's true. The problem is usually heavy plugins, uncompressed images, poor hosting, and overbuilt layouts. I use a lightweight base theme, keep the plugin stack minimal and vetted, compress all images, and configure server-side caching. Sites I build typically score 85+ on Google PageSpeed Insights mobile. Speed is something I test, not just claim.
What's actually included in an Elementor build?
+
The full setup: hosting configuration, WordPress installation, Elementor Pro configuration, global brand kit, header and footer design, all agreed pages built and populated with your content, form setup and testing, basic SEO configuration, and a speed optimisation pass before launch. You get a working, tested, optimised site — not a skeleton needing ten more hours to actually function. Scope is agreed in writing before I start anything.
Can I build new pages myself after you finish?
+
Yes, and that's a specific goal I design for. I set up a library of saved sections and templates inside your Elementor account — your standard service section, testimonial block, CTA panel — so you're not building from scratch when you add a new page. At handover I record a site-specific Loom video walking you through how to create a new page, use saved templates, and update existing sections.
Does the Elementor Pro licence cost extra?
+
Elementor Pro costs around $59/year for a single site, which you purchase in your own name. I'll walk you through that during onboarding. This is your licence, not a shared agency licence — it doesn't disappear if you stop working with me. I'll let you know if any other paid plugins are required for your specific project before you commit to anything.
Can I add WooCommerce to my Elementor site later?
+
It's doable, and Elementor Pro has dedicated WooCommerce builder features that make it cleaner than most alternatives. If you know you'll want e-commerce in the future, tell me before I start — I'll make structural decisions at the build stage that make adding WooCommerce later far less painful. Retrofitting a shop onto a site not designed for it is always more work than scoping it properly from the beginning.
