Every question, organized by what you're building.

Whatever fits the project: Webflow, Wix, or Squarespace for no-code builds, or fully custom development on Astro, WordPress, or Shopify. We pick the stack based on what the business actually needs, not what we're most used to reaching for.

Yes. Web Maintenance & Security is one of our core services: core updates, backups, uptime and security monitoring, with pricing shown directly on that service page.

It depends on scope. A no-code site can move in days, while a custom build or a full SEO/CRO engagement takes longer. We'll give you a real timeline once we understand what you're building, not a generic estimate.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: the scope we'd recommend and the stack that makes the most of it. No budget in mind yet? That's fine too. Describe what you're building and we'll review it and come back with a scoped quote, usually within a day. The one exception is Web Maintenance & Security, which has fixed monthly plans listed on its page.

Yes. A lot of our work starts with a site that already exists: speed and SEO fixes, conversion improvements, tracking cleanups, or ongoing maintenance. We only recommend a rebuild when fixing the current site would cost more than starting clean.

Yes, most of our clients are outside the Philippines. We keep collaboration friendly across time zones: clear written updates, recorded walkthroughs, and scheduled calls when a conversation is faster.

We're a small, focused team: not a single freelancer, and not a large agency. You work directly with the people actually building your project.

Both are great when they fit, and we build on them too. A custom build is for when the site needs something a template genuinely can't deliver: custom features, serious speed requirements, or an interface no theme supports.

The project, every time. There is no single stack we force on every build. Astro is our usual pick for content-focused marketing sites because it produces very fast pages, React fits interactive app-like builds, and plain hand-written code covers the rest. We choose what fits your project best.

Yes, if you need to. We can connect the site to an editing dashboard so your team updates pages without touching code, or keep it fully static if the content rarely changes. We agree on this with you before anything is built.

Yes. Direct integration is a core part of what makes a custom build different from a template site. Booking systems, payment processors, internal tools: whatever the project needs, wired in properly rather than patched together with plugins.

Those pages cover builds on WordPress and Shopify specifically. This page is for hand-built custom sites and lighter web apps that don't fit a platform. If what you need is a full software product behind a login, contact us and we'll scope that directly.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: the scope we'd recommend and the stack that makes the most of it. No budget in mind yet? Describe what you're building and we'll review it and come back with a scoped quote, usually within a day.

Most client work is covered under NDA, so we can't list it publicly. This site is a live example though: primocollab.com itself is a hand-built custom site. Reach out and we will walk you through relevant examples that match what you're building.

Yes. We build under NDA for design, dev, and marketing agencies who need extra development capacity. Deliverables carry your branding, not ours, and you set your own pricing to your client.

Yes, when it's the right fit, and we also build fully custom, hand-coded themes for better performance. Which one makes sense depends on your budget, timeline, and what the site needs to do, and we'll walk you through that before recommending either.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: a custom theme with ACF architecture takes more time than a page-builder cleanup, and a 5-page brochure site is a different project than a WooCommerce store. No budget in mind yet? Describe what your site needs to do and we'll come back with a scoped quote, usually within a day.

Yes. Every editable region is a real ACF field in your WP admin, not hardcoded in the theme. If it should be editable, it is.

Yes. We take on one-time fixes for a specific, pre-existing issue, scoped separately from a full rebuild. If what you actually need is ongoing checks and the fixes that come with them, that's what Web Maintenance & Security covers.

Yes. Performance is built in from the start, not bolted on after. For sites that need the extra edge, we can also implement it a different way behind the scenes (what's called "headless"), which we'll walk you through if it's the right fit for your project.

Yes. Every migration follows SEO best practices, including a full redirect plan and preserved metadata, so the rankings and traffic you've already earned carry over instead of resetting to zero.

In most cases, yes. Your existing pages, posts, and images migrate over during the build. Some things, like certain custom fields or plugin-specific data, don't always survive a cross-platform migration cleanly, and in those cases we'll tell you upfront if it's better rebuilt than migrated.

Yes. We build and customize WooCommerce stores too: product pages, checkout, and the theme all built to the same standard as the rest of the site.

Most of our client work is covered under NDA, so we can't list it publicly. Reach out and we'll walk you through relevant examples that match what you're building.

Yes. We build under NDA for design, dev, and marketing/SEO agencies who need extra development capacity. Deliverables carry your branding, not ours, and you set your own pricing to your client.

For most product-based businesses, yes. Shopify handles the technical heavy lifting (checkout, hosting, security) so you can focus on the store itself. If you're still deciding, reach out and we'll walk you through whether it actually fits before you commit to anything.

It depends on your budget, timeline, and how much performance and customization you need. A theme-based setup gets you live fastest; custom theme development gives full brand control; headless is for stores that need the fastest, most optimized experience possible. We'll walk you through which one fits before recommending any of them.

Yes. Your products, customer accounts, and order history migrate over during the move. Some things, like platform-specific apps or custom checkout logic, don't always survive a cross-platform migration cleanly, and in those cases we'll tell you upfront if it's better rebuilt than migrated.

Yes. Every migration follows SEO best practices, including a full redirect plan and preserved metadata, so the rankings and traffic you've already earned carry over instead of resetting to zero.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: a custom or headless build takes more time than a theme-based setup, and a migration with a large product catalog is a different project than a fresh store. No budget in mind yet? Describe your store and we'll come back with a scoped quote, usually within a day.

Flexible hourly blocks covering CRO, SEO, pagespeed optimization, and general ongoing development, scoped to what your store needs that month, not a fixed package with features you're not using. No retainer is required to work with us on a one-time build.

Yes. Inventory and fulfillment systems, email/SMS marketing platforms, subscription apps, and custom internal tools. If it needs to talk to your Shopify store, that's part of the same ongoing partnership.

Most of our client work is covered under NDA, so we can't list it publicly. Reach out and we'll walk you through relevant examples that match what you're building.

Yes. We build under NDA for design, dev, and marketing/SEO agencies who need extra development capacity. Deliverables carry your branding, not ours, and you set your own pricing to your client.

Uptime monitoring is automated and runs 24/7. Human technical support hours are 5 PM to 5 AM Pacific (8 AM to 8 PM Philippine time), Monday through Friday. Anything submitted outside that window is picked up first thing when we're back.

Daily scans and security monitoring run on every plan. Full malware removal and hacked-site repair are included from the Business plan up. If you're on Starter and something gets through, we'll assess the damage and quote the cleanup honestly before touching anything.

No. Every update runs on staging first specifically so a broken update never reaches your live site in the first place.

Yes, anytime your traffic or needs grow. The difference is prorated, no need to wait for a renewal date.

Yes. Web Maintenance & Security pairs naturally with any of our development services, whether that's a WordPress rebuild, a Shopify theme, or a custom Astro site.

Yes. The plans on this page are built around WordPress, but we also maintain Shopify, custom-built, and other sites. Those are scoped and quoted individually: tell us what your site runs on and we'll come back with a quote, usually within a day.

Yes, and that's the point of Webflow. You edit text and images directly on the page and publish with one click. The layout, fonts, spacing, and colors are locked into the design system we build, so an edit can change what the site says but never how it looks.

For marketing sites, usually. Webflow removes the plugin updates, security patches, and hosting maintenance WordPress needs, and edits can't break the design. WordPress still wins for plugin-heavy builds like memberships or large stores. We build on both, so you'll get the honest recommendation for your case, not the one we happen to sell.

Your pages, posts, and images carry over, and we set up redirects so the Google rankings you've earned follow you to the new site. Some things, like data locked inside a specific WordPress plugin, are sometimes better rebuilt than migrated, and we'll flag those upfront rather than discover them later.

Webflow charges its own hosting subscription, paid directly to Webflow and separate from our build fee. For most business sites it lands in the range of a mid-tier WordPress hosting plan, except hosting, security, updates, and the CMS are all included. We'll recommend the right plan for your site during scoping.

No. Templates are how sites end up looking like everyone else's. We design around your content, your buyers, and your brand, then build it in Webflow from scratch.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: page count, content readiness, CMS complexity, migration size, and custom interactions all shape the build. A focused marketing site is a different project than a 40-page site with three content types. No budget in mind yet? Describe what you need and we'll come back with a scoped quote, usually within a day.

Most of our client work is covered under NDA, so we can't list it publicly. Reach out and we'll walk you through relevant examples that match what you're building.

Then we'll tell you before you spend anything. Some projects genuinely need WordPress, Shopify, or custom development, and we build on those too, so the recommendation you get is based on fit, not on the only tool we know.

For local and service businesses, absolutely. The "Wix looks cheap" reputation comes from DIY setups, not from the platform. Set up properly, you get a professional site with bookings, payments, and hosting in one subscription. It does have ceilings: very large catalogs and heavily custom features belong on other platforms, and we'll tell you if your plans point that way.

Because the platform being easy to edit doesn't make it easy to get right. We handle the structure, the design, the local SEO groundwork, and a bookings setup that matches how your business actually runs. You skip the weeks of evenings fiddling with it, and the homemade look that usually comes with them.

Yes. Wix Bookings handles services, staff schedules, deposits, and automatic reminders, and payments can be taken at booking or on-site. Payment options vary by country, so we'll confirm the right payment setup for your market during scoping.

Honestly, it depends what you count. WordPress hosting can cost less per month, but it needs updates, security, and maintenance time, either yours or a developer's. Wix bundles hosting, security, updates, and bookings into one subscription with nothing to maintain. For a small service business, Wix is usually the lower total effort.

Wix charges its own subscription, paid directly to Wix and separate from our build fee. The right plan depends on whether you need bookings and online payments, and we'll recommend the one that fits during scoping instead of defaulting to the most expensive tier.

Yes, including from your phone. Change prices, update hours, add photos, and manage bookings from the Wix app. Handoff includes a training call where you make real changes yourself, plus a short recording to rewatch later.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: page count, whether bookings and payments are part of the build, content and photo readiness, and any migration all shape the project. A straightforward local business site is a quick one. No budget in mind yet? Describe what you need and we'll come back with a scoped quote, usually within a day.

Most of our client work is covered under NDA, so we can't list it publicly. Reach out and we'll walk you through relevant examples that match what you're building.

Squarespace leans toward design polish: galleries, portfolios, blogging, and newsletters that look editorial out of the gate. Wix leans toward all-in-one business tools like bookings and payments. If your site's job is to present work beautifully, Squarespace usually fits. If it's to run a service counter, Wix usually fits. We build on both and will recommend the one that matches your business.

WordPress makes sense when a site needs plugins, complex features, or a big content operation, and it brings updates and maintenance with it. For a portfolio or studio site, Squarespace gives you the polish without any of the upkeep: hosting, security, and updates are part of the subscription. If your plans genuinely call for WordPress, we build that too and we'll say so.

Yes, at the scale most studios need. Squarespace commerce handles prints, small product lines, gift cards, and appointment scheduling. If you're planning a serious store with a large catalog, that's Shopify territory, and we'll tell you before you invest in the wrong platform.

Yes, if the images are handled properly, and that's part of the build. We prepare and optimize every image so galleries load fast without visible quality loss, on hotel wifi and on phones, not just on your studio machine.

Yes. Your domain moves with you, and pages, posts, and images carry over, with redirects so anything you've earned in Google follows. If something is better rebuilt than migrated, we'll flag it upfront.

Squarespace charges its own subscription, paid directly to Squarespace and separate from our build fee. Hosting, SSL, and updates are included in it. We'll recommend the right plan for what your site sells and shows during scoping.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: how many pages and galleries you need, content readiness, whether commerce or scheduling is part of the build, and migration size all shape the project. A focused portfolio is a quick one. No budget in mind yet? Describe what you need and we'll come back with a scoped quote, usually within a day.

Most of our client work is covered under NDA, so we can't list it publicly. Reach out and we'll walk you through relevant examples that match what you're building.

No. Content strategy, copywriting, and link building are separate disciplines with their own specialists, and we don't try to be all of them. We handle the technical side: the fixes that need a developer to ship. If you need content or backlinks too, we're happy to point you toward people who focus on that.

Anything that requires touching code to fix: Core Web Vitals and pagespeed, schema and structured data, crawlability and indexation, redirect and migration handling, and AI search readiness (llms.txt, structured content, page formatting). If the fix means changing the site itself rather than the words on it, that's us.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: a pagespeed and Core Web Vitals pass is a different project than a full crawlability overhaul, and a migration adds its own scope. No budget in mind yet? Describe the site and we'll come back with a scoped quote, usually within a day.

Both, depending on what you need. Some clients want a focused audit-and-fix pass; others fold technical SEO into an ongoing retainer alongside other development work. Neither is required to start with the other.

Yes, that's often exactly how it works. If you already have a strategy, content plan, or an audit sitting in a backlog, hand us the technical items and we'll ship them without needing to be looped into the rest of your marketing plan.

Yes, and it's often the best time to do it. Technical SEO issues are easier to fix while a site is already being rebuilt than to retrofit afterward. If you're already working with us on a platform build or migration, this can be scoped in together.

It's the technical side of showing up in AI answers: structured data, llms.txt, and page formatting that let tools like ChatGPT and Perplexity actually crawl and cite the site correctly. It's not content strategy or PR aimed at getting mentioned by AI. That's a different discipline, and one we don't offer.

Yes. We work under NDA for design, dev, and marketing/SEO agencies who need technical execution capacity. Deliverables carry your branding, not ours, and you set your own pricing to your client.

Most of our client work is covered under NDA, so we can't list it publicly. Reach out and we'll walk you through relevant examples that match your situation.

Yes, though the approach shifts. True A/B testing needs enough visitors to reach statistical confidence, so on lower-traffic sites we lean more on heuristic review, session recordings, and directional testing, with changes backed by clear evidence, validated over a longer window instead of a fast split test. Either way, decisions come from evidence, not a guess.

Most sites need at least basic analytics in place before testing starts, since that's part of how we measure results. If yours isn't set up yet, we can get it in place as part of getting started, or pair this with Analytics & Tracking if your setup needs a deeper fix.

Whatever the research points to: headlines, calls to action, page layout, forms, pricing presentation, checkout flow. We don't start with a fixed list of things to change; we start with where visitors are actually getting stuck.

The audit and research phase surfaces the first real findings within the first few weeks. How long an individual test takes to reach a confident result depends on your traffic, but the program is built to compound: each shipped win becomes the new baseline the next test has to beat.

No. CRO works with targeted, evidence-based changes to what you already have, not a rebuild. If a bigger redesign turns out to be the right call, we'll tell you plainly and scope it separately.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: traffic volume, how many pages or funnels are in scope, and the testing cadence all shape the program. No budget in mind yet? Describe the site and we'll come back with a scoped quote, usually within a day.

Most client work is covered under NDA, so we can't list it publicly. Reach out and we'll walk you through relevant examples that match your situation.

Yes. We run testing programs under NDA for design, dev, and marketing/SEO agencies who need CRO capacity. Deliverables carry your branding, not ours, and you set your own pricing to your client.

Both. GA4 is usually the center of it, but conversion tracking for Google Ads and the Meta Pixel gets wired and deduplicated too, so the numbers line up across every platform you check, not just the one dashboard you happen to open most.

Yes. It gets wired directly to your real order or lead data, so the revenue in GA4 matches what actually came in, not a default checkout-step estimate.

Consent mode and privacy-safe configuration are part of any tracking setup we do, not a separate add-on.

Yes, and it's one of the most common calls we get. Tracking breaks silently during a redesign or migration since it's rarely tested before launch, and nobody notices until the reports look wrong weeks later.

Built-in store analytics are a reasonable start, but they usually miss marketing attribution, ad-platform conversion data, and a real cross-channel view. This fills that gap rather than replacing what you already have.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: how many events and conversions need tracking, how many ad platforms are involved, and whether it's a fresh setup or an audit-and-fix all shape the scope. No budget in mind yet? Describe your setup and we'll come back with a scoped quote, usually within a day.

Most client work is covered under NDA, so we can't list it publicly. Reach out and we'll walk you through relevant examples that match your situation.

Yes. We handle analytics and tracking under NDA for marketing and SEO agencies who need this capacity without hiring for it. Deliverables carry your branding, not ours, and you set your own pricing to your client.

No. It's built to remove the repetitive busywork sitting in front of your team, not the team itself. Human checkpoints stay wherever judgment, tone, or a final decision actually matters.

Whatever you already use: Gmail, Slack, Google Sheets or Airtable, your CRM, Shopify or WooCommerce, plus an AI step for the parts that need judgment, like drafting or classifying. We wire into your existing tools rather than asking you to rip and replace them.

We scope exactly what data each step touches before anything is built, and sensitive data is only ever passed to an AI step when it's actually necessary and you've agreed to it.

That's what the human checkpoints are for. Anything the AI drafts or flags gets reviewed before it goes out, and every workflow gets error handling for the step that fails silently at 2am, not just the happy path.

You could, and those are real, capable tools. The value here is doing the mapping properly, getting the AI steps and error handling right the first time, and maintaining it afterward, instead of your team learning a new tool on top of an already full plate.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: how many workflows are in scope, how many tools they touch, and how much of each process needs an AI step all shape the build. No budget in mind yet? Describe the process you want off your plate and we'll come back with a scoped quote, usually within a day.

Most client work is covered under NDA, so we can't list it publicly. Reach out and we'll walk you through relevant examples that match your situation.

Yes. We build automation workflows under NDA for agencies who need this capacity without hiring for it. Deliverables carry your branding, not ours, and you set your own pricing to your client.

AI & Workflow Automation handles ops work across the tools you use to run the business, like email, your CRM, and spreadsheets. This is deeper: an agent wired directly into your website or store's own content and commerce backend, through WP-CLI, WPGraphQL, or the Shopify Admin API, so it can make real changes to the site itself.

That's what the guardrails are for: scoped access, staging first for anything risky, a full audit trail of every action, human approval before anything irreversible ships, and version history so any change can be rolled back.

No. We operate the agent on your behalf, or train your team to run it themselves if you'd rather keep it in-house.

WordPress, through WP-CLI and WPGraphQL, and Shopify, through the Admin API. Other platforms are considered case by case if there's a real API or CLI to wire into.

For a large class of routine, well-defined work like bulk edits, migrations, and structured content or catalog updates, yes. Genuinely novel work or real judgment calls still benefit from a developer.

No. This isn't customer-facing at all. It's an internal tool your team uses to manage the site faster; nothing a site visitor ever sees or talks to.

The most useful starting point is your budget. Tell us the number you have in mind and we'll tell you honestly what it can get you: the platform, how much access the agent needs, and how many routine tasks are in scope all shape the build. No budget in mind yet? Describe your stack and we'll come back with a scoped quote, usually within a day.

Most client work is covered under NDA, so we can't list it publicly. This site is a live example though: primocollab.com runs on a headless WordPress backend managed through this exact agentic CLI workflow. Reach out and we'll walk you through it.

Yes. We set up and operate this under NDA for agencies who want the capability without building it themselves. Deliverables carry your branding, not ours, and you set your own pricing to your client.

Create a ticket with what you want changed and where, and attach a screenshot if it helps. Small content changes are usually handled quickly; anything that affects layout or functionality gets a short confirmation of scope first so there are no surprises.

Use the chat box for anything urgent, and mark your ticket as urgent if chat is offline. Site-down issues jump the queue ahead of everything else, and you'll get updates as we work rather than silence until it's fixed.

Urgent issues like a site being down are picked up as soon as possible, ahead of all other work. Standard requests get a first reply within one business day. If something will take longer, you'll get a realistic timeline upfront instead of a vague acknowledgement.

Bigger work is scoped as a small project so nothing is squeezed into support quality. Use the additional work option, describe what you're after, and you'll get a quote with honest numbers, the same way any project here starts.

The same developer who built or maintains your site. There's no outsourced help desk reading from a script, which is why answers tend to be specific and fixes tend to be fast.

No. Tickets and chat work with the email address we already have on file for your project. If you're not sure which email that is, ask in chat and we'll sort it out.