Skip to main content
Convertica Studio
Service 03 — Custom development

You are renting functionality you should own.

Bundles, upsells, filters, finders, size guides, back-in-stock. Six apps, six subscriptions, six script tags you cannot style or measure. We build the ones that matter into your theme, where they belong.

The maths

What a typical conversion stack actually costs.

Six common apps, at published pricing. None of them can be styled to match your store, and each one adds a script to every page.

Rented Per month What we build instead
Product bundles $29–$79 Bundle logic that lives in your theme, priced by real automatic discounts.
Upsell / cross-sell $49–$99 Pairing rules driven by your own metafields, in the buy box and the cart.
Product filters $19–$59 Faceted filtering built on Shopify search, indexed and crawlable.
Product finders / quizzes $39–$149 Guided selling that writes to the URL, so results are shareable and rankable.
Size / fit guides $15–$39 Sizing data as structured metafields, reusable across every template.
Back-in-stock $19–$49 Native notify-me with designed empty and success states.
Total $170–$474 $2,040–$5,688 a year, every year, forever.

Some apps are worth renting — reviews and subscriptions own data we have no business rebuilding. The point is that the decision should be made deliberately rather than by default.

What we build

Eight things worth owning.

Everything here has shipped inside the six themes we sell — which is the reason we can quote it honestly rather than optimistically.

01 Theme architecture

Sections your merchandisers can actually use

Reorderable, per-section settings, designed empty states. Nobody files a ticket to change a headline.

02 Data model

Metafield-driven product data

Scent notes, ingredient lists, fit charts, dosage — modelled once, then powering cards, filters, finders and structured data.

03 Conversion

Guided selling and finders

Multi-step finders that read intent and return three confident answers instead of forty products.

04 Conversion

Buy box and cart logic

Variant behaviour, bundles, pairing, free-shipping thresholds and the reassurance that belongs beside the button.

05 Discovery

Search and filtering

Faceted, fast, crawlable — built on Shopify search rather than a third-party index that goes stale.

06 Visibility

Structured data and feeds

Product, Offer, FAQ and Breadcrumb schema emitted from real fields, so search and AI answers stay accurate.

07 Integration

Third-party integrations

Subscriptions, reviews, ERP and fulfilment wired properly, with fallbacks when they fail.

08 Performance

Performance work

Removing what the app stack left behind: duplicate scripts, blocking assets, layout shift.

Standards

Six rules every build follows.

Custom code that only its author can maintain is a liability dressed as an asset. These are the constraints that stop that happening.

Survives Shopify updates

Built on OS 2.0 primitives — sections, blocks, metafields — not on hacks that break at the next platform release.

Survives your next merchandiser

Everything configurable is exposed as a setting. Hardcoded copy is a defect, not a shortcut.

Degrades honestly

If an integration is down, the section hides rather than showing a broken shell. Empty states are designed, not discovered.

Documented where it matters

A written guide for the parts that are not self-evident, so the next developer is not reverse-engineering your store.

No required apps

If we build it, it does not carry a subscription. The exception is where an app genuinely owns the data — reviews, subscriptions.

Measured after launch

Custom work is judged against the baseline the audit set, the same as a rebuild.

Proof

Six themes, zero required apps.

The clearest evidence that this works is that we sell it. Every theme in our catalogue ships finders, filters, upsells, bundles and honesty-gated proof built in — no subscriptions, no injected scripts. The same components are what we build into client stores.

0 Apps required
393 Sections shipped
Browse the themes

The same components, measured in a client store: Vexivo: Reduced Bounce Rate by 28%. Every build is judged against the baseline the audit set — watch the published audits.

Engagements

Three ways to buy it.

All three are quoted from a written brief with defined edge cases. If discovery proves the brief wrong, we re-quote before continuing.

1–3 weeks

Single build

One piece of functionality, specified and shipped.

  • Scoped from a written brief
  • Built in your theme
  • Documented and handed over
  • Thirty-day defect window
Quoted per scope
3–6 weeks Most chosen

App-stack replacement

Audit the stack, rebuild what should never have been rented.

  • Stack audit with monthly cost
  • Functionality rebuilt natively
  • Data migrated, not abandoned
  • Performance measured before and after
Quoted per scope
Ongoing

Retained development

A standing allocation for stores that ship continuously.

  • Priority queue
  • Monthly roadmap review
  • Fixed monthly allocation
  • Same team, no re-onboarding
Monthly retainer
Fair questions

Build versus rent, honestly.

Including the cases where renting is the right answer and we will tell you so.

Sometimes you should rent it — reviews and subscriptions own data we have no business rebuilding. But most conversion apps inject scripts you cannot style, cannot measure and cannot remove, and charge monthly forever. Six typical apps cost $2,000–$5,700 a year. If the functionality is core to how your store sells, owning it is cheaper by year one and faster on every page load.

Not if it is built on OS 2.0 primitives. We use sections, blocks and metafields rather than Liquid hacks or DOM injection, which is exactly why the themes we sell have shipped updates without breaking anyone. Anything genuinely fragile gets flagged before it is quoted.

You own the code and the documentation. There is no license key, no hosted component and no dependency on us staying engaged. That is the difference between custom development and a bespoke app.

Usually, and we will read it first and tell you honestly whether extending it is cheaper than replacing it. Building on a foundation we would not have chosen is sometimes the right call; pretending it is fine when it is not costs you twice.

From a written brief with defined edge cases. Fixed price, fixed scope. If discovery reveals the brief was wrong, we re-quote before continuing rather than silently absorbing it or silently billing it.

Yes, and it is often the highest-return custom engagement — most Shopify stores are carrying three or four abandoned app scripts. We measure first, so you see what the work bought.

Eight recurring shapes: sections your merchandisers can use without filing a ticket; metafield-driven product data that powers cards, filters, finders and structured data from one model; guided selling and multi-step finders; buy box and cart logic — variants, bundles, pairing, thresholds; faceted search and filtering built on Shopify search so it stays crawlable; structured data and feeds; third-party integrations wired with fallbacks; and performance work that removes what the app stack left behind.

The recurring six: product bundles ($29–$79 a month), upsell and cross-sell ($49–$99), product filters ($19–$59), finders and quizzes ($39–$149), size and fit guides ($15–$39), and back-in-stock ($19–$49). Each is rebuilt natively — bundle logic priced by real automatic discounts, pairing rules driven by your own metafields, sizing as structured data. The exception is where an app genuinely owns the data, like reviews and subscriptions.

Three. A single build, one to three weeks: one piece of functionality scoped from a written brief, built in your theme, documented, with a thirty-day defect window. An app-stack replacement, three to six weeks: a stack audit with its real monthly cost, the functionality rebuilt natively, data migrated rather than abandoned, and performance measured before and after. Or retained development — a fixed monthly allocation with a priority queue for stores that ship continuously.

Six, and they are the same ones our themes are held to: it survives Shopify updates because it is built on OS 2.0 primitives; it survives your next merchandiser because everything configurable is a setting; it degrades honestly when an integration fails; it is documented where it matters; it carries no required app subscriptions; and it is measured after launch against the baseline the audit set.

Send us your app list.

We'll tell you what is worth owning, what is worth keeping, and what is quietly slowing every page down. It comes back inside the free audit.

What happens if you enquire
01
You send the store About forty seconds. No call required.
02
We record the audit Two to three business days. Free, no obligation.
03
You get a scope and a number Written and fixed, before anything starts.