We build and run the systems behind your business.
For experience businesses selling scheduled sessions, visits and access. Fenro builds and runs the website, bookings, payments, memberships and staff tools behind your operation, shaped around how your business actually works. Then we keep the whole system running.
Most software starts with its own model. We start with yours.
Off-the-shelf platforms arrive with a fixed idea of how a business like yours should work. You choose from the workflows and rules the software supports, then work around whatever it doesn't. Fenro works the other way round. We start with how your operation actually runs: what customers buy, how capacity works, what staff need to do, which rules apply and where the exceptions happen. Then we reuse what fits, connect what should stay, and engineer the parts your operation needs where existing software doesn't provide them.
Typical software
- The software defines the model
- Your process adapts to it
- Workarounds handle the exceptions
Fenro
- Your operation defines the rules
- Fenro shapes the system around them
- Customers and staff work from one operation
Shared foundations. Custom where it matters. Operated by Fenro.
Starting with your operation doesn't mean starting from a blank page, and it doesn't mean squeezing your business through whatever a product happens to support. It means deciding, deliberately, which of these five things each part of your operation needs.
Reuse what already solves the problem.
Booking, checkout, payment, membership and admin patterns Fenro has already proven in a live system. You are not paying for those to be invented again.
Configure what should vary.
Your pricing, your capacity, your booking and cancellation rules, what a membership entitles someone to. Settings the business changes, not a job for an engineer.
Integrate what should stay.
Software that already works for you stays, connected properly. We do not replace something just because we could rebuild it.
Build what the operation actually needs.
When the required behaviour isn't supported cleanly by the systems already in place, Fenro engineers that capability instead of handing you a workaround. This is the part that makes the rest of it credible.
Then run the whole thing.
One system, one accountable partner, after launch as much as before it.
What that adds up to
Not a template you have to fit your business into, and not an open-ended software project either. Fenro works in one domain and brings real foundations to every build, so the engineering effort goes where your operation genuinely needs it rather than into rebuilding what already works. Then Fenro stays responsible for running the result.
Customers can book online. Staff can sell at the desk. Why does it still feel like two different businesses?
The problem is rarely one missing feature. It's usually that the customer journey, booking rules, payments and staff workflows have grown into separate pieces that someone still has to hold together manually.
Who this is for
Established businesses selling access to a place, a resource or a scheduled experience. We start with recovery and wellness, then work selectively across sports and activity venues, attractions, classes and tours.
- Recovery & wellness
- Sports facilities
- Activities & experiences
- Attractions & visitor venues
- Classes & workshops
- Tours
What usually brings someone here
What's visible from outside
- Customers struggle to see what is available
- Booking and payment feel like separate journeys
- The mobile experience loses people before checkout
- Memberships or packages are hard to explain
What's broken underneath
- Online and front-desk sales need manual reconciliation
- Staff work around software that does not fit the operation
- Several suppliers are involved, but the owner still fixes everything
Built around a real operation, not a template.
The Recovery Club sells shared recovery sessions, memberships and team bookings. Customers and staff both create bookings against the same real capacity.
Those journeys don't all follow the same rules. Public customers need to give booking notice, and the earliest sessions have to be known about the night before so equipment is ready. Staff still need to take a walk-in from someone standing at the desk. Ordinary sessions are sold per person, while team sessions use a different commercial model entirely.
Fenro shaped those rules into one operation that customers and staff both work from. Some of those rules could be configured. Others required Fenro to engineer behaviour the underlying booking system didn't provide, rather than asking the business to work around the limitation.
The public site is the part you can see. Behind it, Fenro built and still runs the availability, capacity, payments, memberships and staff workflow, and the recovery path for when one of the systems underneath disagrees with another. See what was shaped around the operation →
One number to get you live. One to keep you live.
Implementation takes your operation from discovery through to go-live for £4,000. Managed Partnership begins when you go live and keeps the agreed system running for £400 a month. Fenro only implements systems it will continue to operate.
Implementation
£4,000
From discovery to go-live
Everything needed to launch, as one number.
- Discovery, messaging and the public website experience
- Booking, availability, checkout and payments
- Memberships, packages, staff administration and custom capability where the operation genuinely requires it
- Hosting, domain, analytics and launch, all managed by Fenro
£2,000 is paid on engagement to begin discovery and implementation. We then map the operation and agree exactly what Fenro will implement. The remaining £2,000 is due before go-live.
Managed Partnership
£400/month
Starts when you go live
Everything Fenro stays responsible for afterward, as one more number.
- Help customers buy,
- Help staff operate,
- Keep it running
Fenro only implements systems it will continue to operate. Managed Partnership begins at go-live, with the first £400 payment due then and £400 a month afterward. Fenro monitors the system and takes responsibility for operational failures, so you are not left watching several systems and diagnosing problems yourself. Either side can end this with 30 days' notice, and your domain and business data leave with you.
Talk through your operation
Fenro doesn't just connect systems. It builds and operates the parts that make them work as one.
Four kinds of responsibility, all of them running today in Fenro's first live experience-business implementation. Your business may need some of them, all of them or a different combination. We scope the operation before we prescribe the software.
Help customers buy
Website and discovery
A clear public experience that explains what people can buy and how it works.
Availability and booking
Customers choose a date, see real capacity and reserve the right session.
Checkout, payments and memberships
The price is checked by the system before checkout, and a membership is recognised live at the point of booking.
Confirmations and self-service
A branded confirmation with session details and payment status, plus a link customers use to cancel or reschedule themselves.
Shape the operation
Capacity and pricing
How much you can sell at once and what it costs, held as settings the business can change, not code. A per-person session and a fixed-price group booking can run through the same operation with different commercial rules.
Booking and cancellation rules
Notice periods, preparation time and refund rules that match how the day actually runs, applied by the system rather than remembered by staff.
Memberships and entitlements
What a membership includes, and what it changes at the point of checkout.
Custom capability where needed
When configuration and integration are not enough, Fenro can engineer the behaviour the operation needs.
Help staff operate
Front-desk and walk-in bookings
Staff sell against the same capacity customers see online, not a second calendar to reconcile later.
Admin workflows
Bookings, customers, memberships, prices and availability managed in one place.
Controlled exceptions
Cancellations, refunds and reschedules staff can handle, including the ones the public rules deliberately do not allow.
Payment recording
Cash, card reader or online, all updating the same booking and financial record.
Keep it running
Managed infrastructure
Fenro runs the hosting, domains, deployment and security underneath. It is not something you manage.
Monitoring and maintenance
The system is watched, updated and supported after launch.
Recovery when systems disagree
When a payment or booking succeeds in one place and fails in another, Fenro records it and gives staff one list to resolve, instead of leaving them to compare systems by hand.
We start with the operation, not the software
Every business has its own details. The discipline stays the same: understand the operation, agree what Fenro is responsible for, build the smallest complete system, then run it.
Understand
We map what you sell, how customers book and pay, what staff do behind the desk, how capacity and pricing work, what memberships entitle people to, and which rules and exceptions your operation really has.
Scope
We agree what existing software stays, what needs connecting, what needs extending, and what Fenro needs to build because the required behaviour isn't supported by what already exists. Just as important: what should not be built at all.
Build
We build the agreed customer and staff operation, including the custom capabilities it depends on and the paths real life takes when a booking, payment or membership does not go to plan.
Operate
We launch it, monitor it, and keep the agreed system running and improving after customers start using it.
Managed Partnership
Launch is the start of the operating relationship, not the end of a project. Fenro stays responsible for the system we agreed to run: monitoring it, maintaining the workflows and connections behind it, and sorting out the failures when the pieces underneath stop behaving as one.
Sensible questions before you hand over the system
Clear scope matters when bookings and payments are involved. These are the answers we would give on a call.
How is Fenro priced?
Implementation is £4,000. £2,000 is paid on engagement, which begins discovery and implementation, and the remaining £2,000 is due before go-live. Discovery is part of Implementation and establishes what Fenro needs to build, configure or connect for the operation, not a new price. Managed Partnership is £400 a month and begins when the system goes live, with the first £400 payment due at go-live. Fenro only implements systems it will continue to operate: Implementation gets you live, Managed Partnership keeps you live. If genuinely new work outside the implemented system comes up later, we agree that separately rather than folding it in quietly. Your agreement sets out the commercial terms, payment schedule, responsibilities and any known provider costs before work starts. Discovery then defines the detailed implementation.
I already have a website. Do you rebuild it, or work with what's there?
Not automatically. We start by looking at what you already have. If it provides a sound base and can support the customer journey and systems we need to operate, it can stay. If it's creating friction or preventing the wider operation working as one, rebuilding it may be the better option. The decision comes from the operation, not from a rule that every Fenro client needs a new website.
Does every business get the same booking system?
No. A private resource, a shared-capacity session and a ticketed event have different rules. We start with your operation, reuse what already fits and build only the missing parts.
Is Fenro building custom software, or configuring something that already exists?
Both, deliberately. Fenro brings a foundation already proven in a live experience business: booking, checkout, payment, membership, admin and infrastructure patterns that can be reused and shaped around a new operation. Software you already have that works well stays and gets connected properly. And where the existing software doesn't support the required behaviour, Fenro builds that capability rather than asking you to work around the gap. That is the part that makes the whole proposition work. What Fenro is not is a general software consultancy that takes on any project from a blank page: we work in one domain, reuse what we have already proven in it, and use paid discovery to define the implementation before the build begins.
Am I locked into Managed Partnership?
No open-ended lock-in. Either side can end Managed Partnership with 30 days' notice, and service runs exactly as normal right up to the end of that period. When it ends, your domain and your business data (customers, bookings, records) come with you. The platform Fenro builds and operates stays Fenro's, the same way you'd take your orders and customer list from Shopify, not their engine.
What has Fenro delivered for an experience business?
The Recovery Club is live and taking customer bookings through a system Fenro built and still operates: the public site, capacity-based bookings that customers and staff share, online and front-desk payments, memberships, team bookings on a different commercial model, and the staff tools around all of it. The Recovery Club page sets out which rules were shaped around that operation and why.
Tell us where the operation gets stuck.
Tell us what you sell, how people book and pay, and what your staff have to fix by hand. We'll look at whether Fenro is a fit. Prefer email? Reach us directly at info@fenrohq.com.
Thanks, we've got it. We reply within one business day.