Everything from one team
Design, build and operations with the same team, from the first call to launch.
A Shopify store on a custom theme, without stacked apps. We measure load time before and after launch, and the measurement sheet comes to you in writing.
12+ projects delivered
every one on deadline, in production
Fixed price and deadline
in writing, and if we slip, the next payment waits
Reply within 24 hours
on working days, to every enquiry
In writingStarting price, on request
A whole store to launch day, on a bespoke theme rather than a bought one.
What slows your store down
Every new requirement is another paid app, and the theme loads slower with each one.
The settings have run out, and support writes back that this theme cannot do it.
The mobile checkout is slow, and most of the started carts stop right there.
Which of these is your project
New store on a custom theme
The store starts from scratch: collection structure, product pages and checkout, with your brand’s own face.
Template replaced
The store runs on a bought template and moves to a custom one. Products and orders stay, and the theme is rebuilt.
Move from another platform
Products, customers and order history brought over, with the old URLs redirected.
Work on the store you already run
The missing piece put in place: a checkout integration, new collection pages, or the load time put right.
From the product page to payment, with your Hungarian providers.
Example
For a fashion brand with 400 products we would start with the collection structure, because that is what decides whether shoppers find anything: filtering by size and colour, collection pages with their own copy. The theme loads only the code a given page actually uses. Delivery options and invoicing sit inside the checkout rather than in a fourth app.
The store’s technical stack
Payments and checkout are not worth rebuilding: that part is compliance and upkeep. The custom work is in the Shopify Liquid theme, which is where a shopper finds the product or does not.
We look at how many products and variants there are, and how you take payment and ship. At the end we say if a theme would do.
You get an itemised list of what goes into the theme and what stays an app. We measure today’s load time: that is the measurement sheet’s first column. That price holds to launch.
Your store is built on its own theme and the checkout stays Shopify’s. We measure load time before launch and after it.
After go-live we measure the load time again, and the finished measurement sheet comes to you.
Who should build it
An online store can be bought from several places, and mid-season you find out who you can actually reach.
In-house developer
Freelancer
Hourly agency
Brecon
Who is accountable for the deadline
You are. They estimate; your company carries the consequence.
Whatever you agree. With no deadline in writing there is nothing to hold.
An hourly rate covers the effort; the date stays an estimate.
Us. The launch date is in the proposal, and if we slip, the next instalment waits.
What happens if the person leaves
The knowledge leaves with them unless it was written down. A new hire, a new ramp-up.
One person, one calendar. If they disappear, the project stops.
People can be swapped, and the ramp-up still takes time.
The theme source, the store accounts and the documentation are yours, so the shop does not stop without us.
What happens to the code
Yours, as it is written.
Depends on the contract. One sentence in it settles the question.
Depends on the contract, and licences and accesses are part of the question.
The theme is yours and the store runs in your own Shopify account, so the content stays yours too.
When this is the better choice
When development runs for years and someone is there to direct it daily.
For small, precisely described work this is often a sound choice.
When the scope only becomes clear as you go and you can carry an open budget.
When the revenue comes through the shop, and the bought theme can no longer do what selling asks of it.
The measurement sheet: every page’s load time, before launch and after.
Every page gets its LCP, INP and CLS written down beside the Core Web Vitals threshold, so you can see where the store stands and where the work is left. The sheet below carries sample data.

This fits you if
We would point you elsewhere if
If you are introducing a company rather than selling products, that is website development.
Two Shopify themes we delivered
70%
is the average share of started carts that never reach payment. A long, complicated checkout is among the most frequently named reasons.
Baymard Institute, a meta-analysis of 50 studies. Not our measurement.
Companies we've built for
On every project
Everything from one team
Design, build and operations with the same team, from the first call to launch.
Your goal sets the bar
The first call is about what you want to achieve; if less will get you there, we say so.
Tested before it goes live
We measure what we hand over before launch, and watch the first week with you, measurements included.
How we work
The proposal is itemised: what we build, by when, for how much.
In writing
Starting price, on request
A whole store to launch day, on a bespoke theme rather than a bought one.
Product count, variants, and the payment and shipping integrations. Migrating an existing store is a separate line.
Get a fixed-price quoteA webshop lives in seasons: campaign traffic and the payment and shipping integrations are what ask for the most follow-up work.
First month
Source code, credentials and documentation in your hands. We watch the first week with you, measurements included.
Every month
Updates, fixes, extensions, and the measurements watched as your product grows.
If something breaks
A first reply within 24 hours on working days, to every enquiry.
The quote covers the custom theme, the collection structure, product setup and the payment and shipping integrations, at a figure agreed after the first call. Migrating an existing store, a second language and custom app development are separate items, each listed in the proposal. Whatever the quote says holds to the end of the project.
Yes, from WooCommerce, from a local platform or from another Shopify theme. Products, customers, order history and redirects from the old URLs are part of the work, so the rankings you have today survive the move.
Yes. Products, prices, collections and copy live in the Shopify admin, and the theme is built from sections you move around in the editor. A developer is needed for a new section type or a new integration.
If you sell a handful of products and the look is secondary, a bought theme is enough, and we will say so on the first call. A custom theme pays off when the brand and the load time make you money: bought themes carry every feature any store might want, and your visitors pay for that in waiting.
At handover you get a maintenance quote of its own: we track Shopify's changes, fix what breaks and extend the theme when a new campaign or feature comes. The store and the theme live in your Shopify account, so everything runs without us too.
Fewer than with a template. What the theme can do, we build into the theme rather than renting it as an app subscription. What remains is what genuinely belongs in an app: invoicing, parcel lockers, newsletter. The quote lists what will run as an app and its monthly fee.
The domain and the URL structure stay, so the rankings stay with them. Where an address does change we put a 301 on it and keep the old list. Before the switch we record the current rankings, so afterwards there is something to measure against.
Half an hour covers the product count, the payment and the shipping. Then you get an itemised proposal, including which apps can stay.