Questions, answered straight.

Both. Alongside WordPress we build custom platforms in Laravel and Vue.js, with the same team and the same long-haul maintenance approach. WordPress is one half of what INFIGO does; bespoke application work is the other.

Because for most platforms we build, the value is in the backend - domain model, queues, integrations, permissions - not in rich client-side interaction. Laravel + Inertia + Vue gives us SPA-smooth navigation without a separate frontend app, a separate deploy, a separate auth layer. When a client needs a full SPA (editors, canvas apps, real-time collaboration), we reach for Vue standalone. We don’t default to it.

Yes. Most of our work has at least one external system in the loop - CRMs, ERPs, payment, identity, data warehouses. We’ve written adapters for Recman, HubSpot, Stripe, Przelewy24, Auth0, SAML/OIDC, S3-compatible storage, countless REST and a few stubborn SOAP endpoints. Integration work is written plainly and tested against real API fixtures.

Yes, for catalogues up to a few thousand SKUs with custom rules - multi-currency, B2B pricing, configurators, integrations with ERP, payment and shipping. Above that, WooCommerce stops being the right tool and we steer you to either headless Woo (Laravel frontend, WP admin) or a different platform entirely. We’ll tell you in the first reply.

Shopify is a good fit when the catalogue is simple, the buyer is a consumer, and the integrations live inside Shopify’s app store. It’s the wrong fit when you need bespoke pricing rules, multi-warehouse logic, B2B account hierarchies, custom checkout flows, or you’d rather own the code than rent the platform. We’ll tell you when Shopify is the cheaper, simpler answer - and then we won’t quote.

WooCommerce when WordPress is already the right home for the rest of the site, the catalogue is in WP’s range, and FacetWP, ACF and a curated plugin set cover the gap. Custom Laravel when the rules are too specific for WP-shaped data - multi-warehouse stock, B2B contracts with per-account pricing, real-time integrations with ERP or carrier APIs, custom checkout flows that violate WooCommerce’s assumptions. The pricing routes the same way: WooCommerce in the WP range, Laravel storefronts in the platform range.

We run sites on provisioned VPS servers, set up the way a developer would: version-controlled deploys, a staging environment, server-level caching and off-server backups. Not shared cPanel hosting behind an FTP password.

Yes, and it is often the cheapest reliability upgrade a site can get. We move it onto a proper server with staging and version control, usually as part of taking the site over for maintenance.

Monitoring that watches the business, not just the server. Most tools tell you a site is down, which is the easy case and the rare one. The expensive failures are quiet: a contact form that stops handing mail to the server after an update, a checkout that fails at payment, an expired certificate, a page still returning 200 with nothing on it. We built GoFirmo for exactly that, because we maintain sites for other people and needed it, and it runs across the ones we look after. The point is that we hear about it before you do.

Only if it sets cookies that are not strictly necessary, which in practice means analytics, advertising or embedded third-party widgets. The banner is not a legal requirement in itself. It is the consequence of a decision to track, and that decision is usually made without anyone asking whether the data will ever be read. Take the trackers out and there is nothing left to ask consent for. If you genuinely need them, for instance because you run ads and have to attribute conversions, then you need the consent layer built properly rather than bolted on.

Only when a client asks for it and understands what comes with it: a consent banner, a transfer of visitor data to a third country, and numbers that are incomplete anyway once people decline. For most business sites we start with Google Search Console, which needs no script and no cookies and answers the more useful question of what people searched for before they arrived. Where on-site behaviour genuinely matters, we use cookieless first-party measurement hosted on the client’s own server, so the data never leaves their infrastructure.

No. On every site we have shipped, we build a custom theme and structure content with ACF Flexible Content, so editors compose pages from modules we designed. No Elementor, Divi or WPBakery.

Yoast, Premium on the larger sites, for titles, meta and sitemaps. Everything else about SEO is structure, content and page speed, which is work, not a plugin.

Contact Form 7 with CFDB7, which stores every submission in the database instead of only emailing it. For complex, multi-step or signed forms we add Formidable or write the logic ourselves.

For page structure we use ACF Flexible Content, and several sites run the Classic Editor. The goal is that a content editor composes brand-safe modules we designed, rather than a freeform layout that drifts from the brand.

With WordPress Multisite: one site per language, each with its own content, URLs and settings, under one install and one codebase. It is how this very site runs (infigo.pl and infigo.dev). Every string in the theme is translatable the standard WordPress way, and the content lives in the CMS, so your editors own the translations. We don’t layer WPML or Polylang on top - a translation plugin bolted onto a single site is a second content model to maintain and the usual source of broken URLs.

Engineering. We build from your Figma, your designer, or a spec. We don’t run a design practice; we’ve seen enough half-designed work to keep those functions separate. We can recommend a handful of designers we’ve shipped with for years.

Yes. A large part of our work is inheriting sites, often after an agency handoff, auditing the plugin pile, and taking it back down to a short list we can maintain for years.

Sure. Send yours with the request, or we’ll send ours. It’s not a bottleneck, we’ve signed plenty and nothing in a first message needs to be secret anyway.

Gdańsk, CET. Much of our long-running work is Nordic, Norwegian and Swedish clients over the years. We invoice in EUR, NOK or PLN; contracts in English or Polish, whichever you prefer.

Projects locked to something we don’t work in (Shopify custom apps, .NET, native mobile). Crypto. Anything where the core business relies on a page-builder we’ve agreed not to touch. And anything where the scope is “we’ll figure it out as we go” without a written plan; that’s a rebuild in year two.