App Stack Audit & Management
Every app scored on cost, script weight, overlap and actual usage. We remove what is redundant and own the relationship with what stays.
Madrid
Shopify Apps & Ongoing Growth Support in Madrid
A named team keeping a Madrid store fast, compliant and improving, working across an eight-hour time difference in writing.
Delivered remotely for brands across Madrid and Spain.
Scale · Madrid
Why Madrid brands come to us for this
- App stack audited on cost, script weight and overlap — invoicing, translation, carriers, consent and payments included
- Translation moved from an app into the theme layer where it belongs, cutting scripts and fixing untranslated strings
- Custom Functions for freight banding, trade minimums and gift-set logic instead of stacked subscriptions
- Quarterly Core Web Vitals and dependency review against Shopify's platform releases, tested for regressions
- Escalation path, response windows and August coverage agreed in writing before you need them
Spanish Shopify stores accumulate a particular app stack, and it is heavier than most. Invoicing, because compliant documents are not optional. Translation, because the store runs in at least two languages. Carrier integrations for the couriers your fulfilment actually uses. A payments layer carrying Bizum and instalments. Cookie consent. Then the usual reviews, loyalty and upsell tools on top. Each one adds a subscription and a script, and nobody has audited the total in two years.
So the first job on a retainer here is usually subtraction. Every app scored on cost, script weight, overlap and whether anyone still uses it. Translation apps that duplicate work the theme should be doing natively get replaced. Two apps doing one job get resolved. Where renting the stack costs more or runs slower than owning the code, we build the Function or the private app instead — freight banding by weight, trade minimums, gift-set logic and bundle pricing are all common candidates in this market.
After that it is cadence. A prioritised backlog, a sprint capacity agreed up front so a known number of items ship each month, quarterly Core Web Vitals and dependency review, and a named developer and strategist who know your store rather than a ticket queue that reintroduces you to a stranger every time something breaks. The store should end the year in demonstrably better shape than it started, and the monthly report should be able to prove it.
Local context
Eight hours apart, so the handoff has to be written
Madrid is eight hours ahead of Mountain Time and the genuinely shared window is about two hours — late afternoon for you, early morning for us. We do not pretend that is an advantage, but it is workable if the process is built for it rather than around it. Standing calls sit in that window and cover decisions only. Everything else is written: specifications, change logs, Loom walkthroughs and a documented backlog you can read at eight in the morning without waiting for anyone to wake up. In practice, work briefed at the end of your day is usually back with you by the next morning, which suits a build-review rhythm well and suits a live incident badly — so for revenue-blocking issues we agree the escalation path, the response window and what your own team is authorised to do first, before you need it rather than during. August is planned around the same way: coverage agreed in advance for the weeks your team is away, and the quiet stretch used for the theme cleanup and dependency work that needs downtime nobody has in October.
Scope
What Apps & Support includes
The same standard of work we run for every client — applied to a Madrid brand’s realities.
Full service detailCustom App & Function Development
Private apps, Shopify Functions and admin extensions built when a subscription stack is more expensive or slower than owning the code.
Theme Maintenance & Speed
Quarterly Core Web Vitals review, dead-code removal, dependency updates and regression testing against Shopify's platform releases.
Priority Bug Support
Named Slack channel with defined response times: two business hours for revenue-blocking issues, one business day for everything else.
Monthly Optimisation Workstream
A ranked backlog of improvements, features and experiments, with an agreed sprint capacity so a fixed number of items ship every month.
Quarterly Roadmap Review
A session on what shipped, what it moved, and what the next quarter should target. Priorities get reset against your commercial plan, not a fixed contract scope.
Scoped and quoted for your Madrid store
We do not work off a rate card. Every Madrid engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.
Get this scopedHow it runs
From kickoff to results
Store Health Check
App stack, theme code, speed, integrations and open bug list documented in the first two weeks. You get the findings whether you continue or not.
Stabilise
Redundant apps removed, urgent bugs cleared, monitoring and staging environments set up. Usually pays for a chunk of the first quarter in cancelled subscriptions.
Backlog & Cadence
A shared, ranked backlog and a fixed sprint rhythm. You always know what is in flight, what is next, and what capacity is left.
Ship Monthly
Two-week sprints with a demo and changelog at the end of each. Work is visible in your own board, not hidden in an agency system.
Review & Reprioritise
Monthly reporting on what shipped and what it moved, then a quarterly reset of priorities against your commercial goals.
Proof
Apps & Support results
Anonymised under NDA. Figures pulled from the client’s own analytics.
Supplements (Subscription DTC)
~$4.2M/yr, 60% subscription revenue, 22 SKUs, US · Shopify Plus (Recharge, Klaviyo)
Monthly subscription churn hit 9.4% and the cancel flow was a single button on a hosted page nobody had touched in three years. Support processed 340 subscription changes a month by hand because customers could not do it themselves. The named constraint: no forced logins. The brand refused to gate account access behind a password reset, which ruled out every off-the-shelf portal.
9.4% → 6.1%monthly subscription churnheld for five consecutive months, not a single-month dip
+34%12-month customer LTV$187 to $251 on the subscriber cohort
19% → 38%of revenue from email + SMScategory benchmark for a healthy program is 25-40%
-71%subscription support tickets340/mo to 98/mo after the self-serve portal launched
Outdoor & Sports Gear
~$7M/yr, 480 SKUs, US + EU via Shopify Markets · Shopify Plus (Shopify Markets, 3 regions)
Paid social carried 81% of revenue and CAC had climbed 44% in eighteen months. Organic sat at 2,100 sessions a month against category competitors doing ten times that, and the EU storefront duplicated the US catalogue with no hreflang at all. The named constraint: three national retailers own the head terms with link profiles this brand could not match in a year, so the plan had to win on query depth instead of authority.
+186%organic sessions2,100 to 6,000/mo, branded queries excluded
+21%conversion rate on organic traffic1.9% to 2.3% after the collection and PDP work landed
$61 → $45blended CACorganic share of revenue went from 8% to 24%
+38%revenue year over yearwith paid media spend down 12%
In their words
Clients on this work
$1,900/mo of app spend cancelled
“First month they cancelled eleven apps we were still paying for, just under $1,900 a month, which covered more than half the retainer before they shipped a line of code. The backlog lives in our own board and we rank it together — it is not a bucket of hours that quietly evaporates. Two years in and I have never had to chase a bug fix twice. We are twenty minutes from their office and they still turn up in person for the quarterly, which I appreciated more than I expected to.”
OwnerSporting goods brand, ~$4M/yr · Albuquerque, NM
Verified client, 2025FAQ
Apps & Support in Madrid — your questions
Partly, and we will be precise about which part. Our morning is your late afternoon, so that window is live. Your morning is our night and it is not covered by anyone awake — so anything urgent in your first hours goes to a documented runbook your team can act on, and reaches us at the start of our day. For most retainer work that is fine. If your business genuinely needs someone answering at nine in the morning Madrid time, we will tell you that we are not the right fit.
It depends on the stack, but the pattern is consistent: keep the ones that do something Shopify genuinely cannot — compliant invoicing and the carrier integrations your fulfilment depends on — and question everything else. Translation usually belongs in the theme rather than an app. Consent tooling has to be a proper CMP wired to consent mode, not a decorative banner. Anything whose job overlaps another app in the list gets resolved to one.
We agree the plan in July rather than discovering it in the first week of August. That means deciding who on your side is contactable and for what, which campaigns and flows keep running at reduced volume, and what we are authorised to change without sign-off. It is also when we schedule the work that benefits from low traffic — theme cleanup, dependency updates, app removals and speed work — so the quiet month produces something rather than just passing.
Not if the boundary is drawn properly, and it often works well. A local developer who can be in the room and works in your timezone covers things we cannot; we tend to take the strategic workstream, the platform work and the areas needing specialist depth. What we insist on is one backlog, one staging environment and a shared change log — two parties editing the same theme without that is how a store ends up needing a rebuild.
A named developer and strategist, an agreed sprint capacity, priority bug support, app stack management and monthly reporting. Capacity is set in hours per month and rolls over one month if unused. Anything outside scope gets quoted separately before work starts.
Three months, then rolling with thirty days' notice. The three months exists because the first month is mostly stabilisation and you would not see the benefit of the arrangement inside a shorter window. We do not do twelve-month lock-ins.
When the subscription cost exceeds roughly $500 a month, when the app injects scripts that hurt Core Web Vitals, or when you need logic no vendor offers. Below that threshold, buying is almost always the right answer and we will say so.
Next step
Apps & Support for your Madrid brand.
Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.
Shopify or Shopify Plus stores doing $150k/mo or moreFounder, CEO or eCommerce lead on the callNo deck and no pitch — we open your store instead
Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.