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.
Custom theme or pre-built?
+
Custom for serious projects. We do not modify ThemeForest themes — too much technical debt downstream.
Will you use Elementor?
+
Yes when it fits. We build custom Elementor templates with brand-system widgets. Not page-builder soup.
How fast will the site be?
+
Lighthouse 90+ mobile is the baseline we ship at. LCP under 2 seconds is the target.
Can I edit content myself?
+
Yes. Every build ships with a custom Gutenberg block library or Elementor template kit so non-technical teams can publish without a developer.
Yes. Subscriptions, memberships, multi-vendor, custom checkout. Stripe, Razorpay, PayPal, all standard.
How long does a WordPress site build take?
+
A standard 5–8 page WordPress site takes 3–5 weeks from signed contract to launch. Week one is setup and design. Weeks two and three are the build. Week four is your review and revision round. Week five is testing and launch. Timeline extends for WooCommerce, large content migrations, or custom functionality. The biggest delays are always client-side: missing content, late feedback, or decision changes mid-build.
Do you build custom themes or use pre-built ones?
+
Both, depending on your budget and requirements. For most SMB sites, I build on a lightweight base theme like GeneratePress or Astra with Elementor handling the page design — fast, flexible, no custom-code fragility. For clients who need something a page builder genuinely can't produce, I scope custom theme development separately. I'll recommend the right approach honestly, not the one that runs up the most hours.
Will I be able to update the site myself after launch?
+
Yes — self-editing is a core requirement I design for. I build every site so that changing text, images, and basic layout on existing pages requires no coding knowledge. I record a site-specific Loom walkthrough at handover so you know exactly how to make common updates. For structural changes like new page templates or custom functionality, you'll want a developer. I won't build a site that holds you hostage to my calendar for routine content updates.
What about site speed and SEO?
+
Speed and basic on-page SEO are built into every project. I configure caching, compress images on upload, use a lightweight theme stack, and set up a CDN if your hosting supports it. Every page gets a proper title tag, meta description, and heading hierarchy. I install and configure Rank Math or Yoast and connect Google Search Console. Ongoing SEO strategy — keyword research, content creation, link building — is a separate service, but the technical foundation will be solid at launch.
What hosting do you recommend?
+
Managed WordPress hosting — typically Kinsta, WP Engine, or Cloudways depending on your budget and traffic. Shared hosting is a false economy: it's slow, support is poor, and security incidents are more common. I set up and configure the hosting environment as part of the build. If you already have hosting you're happy with, I'll work within it — but I'll give you an honest assessment of whether it's suitable before we start.
What happens if something breaks after launch?
+
Every site I launch comes with a 30-day post-launch support window. If something breaks due to my build, I fix it at no charge. If the issue is caused by a plugin update you ran or content you added, that's billable support. After 30 days, I offer ongoing maintenance retainers or ad-hoc support billed hourly. Either way, you'll have a developer who knows your specific site available, not a generic support ticket queue.
