Case study · WordPress

Carry On Services: A WooCommerce Build for Medical Transport | Digital Heroes

WordPress Development product interface illustration for Carry ON Services Client Case Study.
The short answer

This case study covers the WordPress and WooCommerce site Digital Heroes built for Carry On Services Inc, a wheelchair accessible medical transportation operator running non emergency medical, private and senior transport across Massachusetts and Rhode Island. It walks through the booking, membership and incident reporting structure visible on the live site today, and is careful to claim nothing that a reader cannot check themselves.

Rides, not products: what Carry On Services actually sells

Carry On Services Inc sells rides. Not products, not software, rides for people who cannot easily drive themselves to the place they have to be. The company runs three named service lines across Massachusetts and Rhode Island: non emergency medical transportation, private transportation, and senior transportation. Each line has its own page on the site, and each one is offered in both wheelchair accessible and ambulatory form.

The detail on the site tells you more than the category label does. The homepage names dialysis, physical therapy and chemotherapy runs directly, which is the recurring end of this market rather than the one off end. There is a section on getting a passenger down and up stairs, which is a separate operational capability from simply owning a lift equipped van. There is a pet friendly rides section, which sounds like a soft touch until you remember that a passenger heading out for a four hour appointment may have nobody to leave an animal with. There is a payment options section, a free membership sign up, and a separate member login for people who have signed up.

Around those service pages sit a booking page, a careers page, a blog, a contact page, a page for a wheelchair training course, and a page for reporting an incident. Thirteen pages in the site's own public page list, and not one of them is filler. The incident report page in particular is the giveaway that this is a working operator and not a brochure. A company that puts strangers into vehicles needs a named place for a complaint to land. The headline the site opens with, Got 99 Problems , But a Ride Ain't One, tells you the tone it wants with families, and the page title tells you the search it wants to win: medical transportation in Massachusetts.

A ride is a harder thing to sell online than a pair of shoes

A product has a price, a size and a stock level. A ride has a date, a pickup time, a pickup address, a destination address, a mobility level, a return leg that may or may not exist, an escort who may or may not travel, and a payer who is frequently not the passenger. Every one of those is a required field before dispatch can act, and every one of them is a field a stressed person has to fill in on a phone.

Start with the payer, because it splits the whole site in two. A ride covered under a Medicaid arrangement is authorised and billed through a completely different path from a ride a family books and pays for directly. The private pay visitor wants to see a price. The covered rider does not have a price at all, they have an eligibility question. A storefront that shows one number to everybody is wrong for a large share of its traffic. That is exactly why a free membership sign up and a member login exist on this site, and why the membership saving is scoped to private pay. The site is separating two audiences that look identical on the way in.

Then take recurrence. Dialysis is not an appointment, it is a schedule: three sessions a week, often for years. Chemotherapy and physical therapy run in courses. If a booking form treats every ride as a fresh one off, the most valuable customer on the book is the one doing the most typing, week after week. Any operator in this category eventually needs standing bookings, and the front end has to be shaped so that a repeat rider is recognised rather than re interviewed every time.

Mobility level is the third trap. Wheelchair, ambulatory and stair assistance are not preferences, they are dispatch constraints. They decide which vehicle rolls and how many crew members are on it. If the booking flow does not capture that cleanly, the operator finds out at the door, with a passenger waiting and an appointment slot burning. The same applies to the appointment time itself: passengers know when they need to be there, not when they need to be collected. The fixed point is the arrival and the pickup is derived backwards from it, which is the opposite of how a normal booking form thinks.

Finally there is the question of who is at the keyboard. The person booking is very often not the person riding. It is an adult child two states away, a group home coordinator, a discharge planner at a clinic. So passenger details and requester details are separate sets of data, the confirmation needs to reach both, and the phone number has to be visible on every single template because a good proportion of this audience will simply call instead. Large tap targets, few required fields and no account wall in front of a first enquiry are not styling choices here. They are the difference between a booking and a bounce.

One more thing this category carries that a retailer does not: a duty of care that produces paperwork. Incidents get reported. Drivers get trained and credentialled. Vehicles get inspected. Two states means two sets of rules and a coverage question that every visitor asks in the first ten seconds. A transport website has to answer where do you drive before it answers anything else.

The WordPress and WooCommerce build Digital Heroes delivered

Digital Heroes built the Carry On Services site on WordPress with WooCommerce. Both are detectable in the technology fingerprint of the live page, so this is not a claim that needs taking on trust.

The structure is service led rather than catalogue led. One page per revenue line, so non emergency medical transportation, private transportation and senior transportation each get their own page and their own explanation instead of becoming three bullet points on a single services page. That matters for search as much as for clarity, because the three lines attract different queries from different people. A daughter searching for senior transportation and a clinic coordinator searching for non emergency medical transportation are not the same visitor and should not land on the same page.

On top of that sits an account layer. The site carries a free membership sign up page and a separate member login page, which is where WooCommerce earns its place. The operator does not need a cart with four thousand line items. It needs customer accounts, a member tier, forms that submit reliably, and content it can edit without a developer. WooCommerce brings the account and order plumbing, and WordPress brings the editing surface for the blog and the service pages.

Then there are the operational pages that many agencies would leave out and this build did not: a booking page, a report an incident page, a careers page, and a page for a wheelchair training course. Careers deserves a note of its own. Vehicle supply is not the constraint in this business, driver supply is. A transport operator recruits continuously, which makes the careers page a second funnel carrying close to the same commercial weight as the booking funnel. Building it as an afterthought is a mistake. Contact details are pinned into the header bar above the navigation on every template, which is the correct call for an audience that converts by phone.

Digital Heroes is the number one ranked Top Rated Seller in website development on Fiverr and is vetted by Fiverr Pro, and the working method behind builds like this one is deliberately unglamorous: the specification is signed before any code is written, so the page list, the account behaviour and the form routing are all agreed while they are still cheap to change.

What an operator in the same position should take from this

The first lesson is that the platform question is usually the wrong question. Owners of service businesses ask whether they need Shopify or WooCommerce or a custom application, when the real question is what the unit of sale is. Carry On Services does not have a catalogue. It has three service lines, an account tier, a booking intake and a set of operational forms. WordPress with WooCommerce covers that at a fraction of the cost and the maintenance burden of a bespoke booking application, and it leaves the client able to publish a blog post without raising a ticket.

The second lesson is that the pages you would cut are often the ones doing the work. Thirteen pages is a small site. But the incident report page, the careers page and the training course page are all load bearing for a regulated, staff dependent operation, and none of them would survive a purely marketing led sitemap review.

The third lesson is about restraint in what a case study can honestly claim. This page tells you what was built and what is visible. It does not tell you how many rides the site has generated, what the conversion rate is, or whether the booking form is wired into a dispatch or billing system, because none of that is visible from outside and none of it can be checked by a reader. Anyone showing you a case study with a revenue figure attached to a website launch is showing you a number that could not be audited even if it were real. Digital Heroes maintains more than seventeen thousand published development guides on this site, and the reason the case studies sit alongside them without invented metrics is that a checkable build is more persuasive than an unverifiable percentage.

Here is the concrete thing to go and check. Open the site, then open the booking page, then open the free membership sign up page, and notice that the member login is a third, separate destination. That three way split is the whole commercial model rendered as navigation: enquire, join, return. Then look at the header bar and see how much room the contact details get above everything else. For this audience that is the primary conversion element, and the build treats it that way.

Research & sources

The evidence behind this guide

Independent findings on why this investment pays off. Every link goes to the primary source.

  1. 73% of surveyed businesses now use a headless architecture (up nearly 40% since 2019), and 98% of those not yet using it are evaluating or planning to evaluate headless within 12 months, with 82% saying it makes delivering consistent content easier. Source: WP Engine (2024) →
  2. Vulnerabilities disclosed across the WordPress ecosystem rose sharply in 2024 (up 68% from 2023), and roughly a third (about 35%) remained unpatched into 2025, with over one-third of developers unreachable or unresponsive to fixing vulnerabilities, underscoring the scale of automated attacks WordPress sites face. Source: Wordfence (Defiant) (2025) →
  3. Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
  4. Poor software quality cost the US economy an estimated $2.41 trillion in 2022, including roughly $1.52 trillion in accumulated technical debt, driven partly by unsuccessful development projects and low-quality legacy systems. Source: Consortium for Information & Software Quality (CISQ) - Herb Krasner (2022) →
Riley T. · Content Strategist · APAC · Sydney

Riley plans content for APAC clients, working out what a site needs to say, in what order, and who it is for before a page gets designed. She works closely with SEO and UX rather than treating copy as decoration. Her posts help readers judge whether their content is doing any work.

View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.

FAQ

Frequently asked questions

What does Carry On Services do?

Carry On Services Inc is a transportation operator running non emergency medical, private and senior transportation across Massachusetts and Rhode Island. Its live site lists all three as separate service lines, each offered in wheelchair accessible and ambulatory form. The homepage names dialysis, physical therapy and chemotherapy runs specifically, alongside stair assistance and pet friendly rides, which tells you it serves recurring clinical appointments rather than occasional one off transfers.

Who built the Carry On Services website?

Digital Heroes built the Carry On Services website on WordPress with WooCommerce. Both platforms are detectable in the technology fingerprint of the live page, so the claim is checkable without taking anyone's word for it. Digital Heroes is the number one ranked Top Rated Seller in website development on Fiverr and is vetted by Fiverr Pro, and it signs a written specification before any code is written.

Why use WooCommerce for a transport company instead of plain WordPress?

Digital Heroes used WooCommerce here for the account layer rather than for a shopping cart. The Carry On Services site carries a free membership sign up page and a separate member login, which means it needs customer accounts, a member tier and reliable form handling. WooCommerce provides that plumbing on top of WordPress without a bespoke application, and WordPress keeps the blog and the three service pages editable by the operator.

Can a WooCommerce site handle bookings instead of physical products?

Digital Heroes built the Carry On Services site on WooCommerce as a booking led structure rather than a product catalogue, with a booking page, three service pages and an account tier. The important design point is that a ride is not a product listing. It carries a date, two addresses, a mobility level, a return leg and a payer, so the intake has to collect dispatch constraints rather than cart options.

What makes a medical transportation website harder to build than a normal service site?

Carry On Services shows the split clearly: a medical transport site has to serve two payer paths at once, which most service sites never face. A privately paid ride has a price. A ride covered under a Medicaid arrangement has an eligibility question instead. That one difference changes pricing display, account structure and the booking form. Add recurring dialysis schedules, wheelchair versus ambulatory dispatch constraints and caregivers booking for someone else, and the intake gets complicated fast.

Why does the Carry On Services site have a member login?

Carry On Services runs a free membership sign up with a saving scoped to private pay riders, so the site needs a member login to hold that relationship. Membership separates two audiences that look identical when they arrive: privately paying families, who want a price, and covered riders, who do not have one. The navigation splits enquiring, joining and returning into three separate destinations, which is the commercial model rendered as structure.

Does Digital Heroes write a specification before building a website?

Digital Heroes signs a specification before any code is written, on every build including this one. For a site like Carry On Services that means the page list, the account behaviour, the booking intake fields and the form routing are agreed while they are still cheap to change. Thirteen public pages sounds small until you notice that the incident report, careers and wheelchair training pages are all operationally load bearing.

Why does a transportation website need a careers page?

Carry On Services runs a careers page because driver supply, not vehicle supply, is the real constraint in passenger transport. An operator in this category recruits continuously, which makes the careers page a second funnel carrying close to the same commercial weight as the booking funnel. Digital Heroes built it as a first class page in the site structure rather than a link buried at the bottom of the footer.

How much of a case study like this can actually be verified?

Digital Heroes limits these case studies to what a stranger can confirm from the live site: the platform fingerprint, the page structure, the service lines, the account pages and the market served. No conversion rate, revenue figure or ride volume appears on this page, because none of those can be checked from outside a business. A build you can open in a browser is stronger evidence than a percentage on a slide.

What should I check on the Carry On Services site myself?

Carry On Services is worth checking in three places: the booking page, the free membership sign up page and the member login, which is a separate destination from both. That three way split shows how the site handles a first enquiry, a member signing up and a rider coming back. Then look at the header bar, where contact details sit above the navigation on every template for an audience that converts by phone.

Should I buy a premium theme like Avada or Divi, or pay for a custom WordPress theme?

Buy the premium theme if you are validating a business or must launch inside two weeks; Avada is $69 one time on ThemeForest and Divi is $89 a year, which is unbeatable at that stage. Go custom when the generic look starts costing you conversions or every small edit means fighting the theme's bundled builder. In Digital Heroes rebuild work, the most common trigger for switching is a premium theme site failing Core Web Vitals after two or three years of accumulated plugins.

What should I prepare before contacting a WordPress agency?

Bring a one page brief: what the site must do, three reference sites you like, a rough page list, your budget range, and your deadline. Also gather logins for your domain registrar, current hosting, Google Analytics, and the existing WordPress admin if you have one, because chasing access routinely eats the first week of a project. You do not need a formal specification; writing one is the agency's job, but they cannot invent your business goals.

How do I vet a WordPress developer before hiring them?

Ask for two live sites they built recently, then run both through PageSpeed Insights yourself; if their portfolio fails Core Web Vitals, your site will too. Follow with three questions: do they use staging environments and version control, do they build on the block editor or a page builder, and who handles updates after launch. Anyone whose workflow is editing the live site over FTP is a future outage you would be paying for.

Can I migrate my Shopify or Wix store to WooCommerce without losing orders and customers?

Yes, products, customers, and order history all export and import cleanly, with one caveat: customer passwords cannot be migrated from Shopify, so buyers will reset them on first login. A typical store migration with data cleanup, redirects, and payment gateway setup takes 3 to 6 weeks. Run the new store on staging in parallel and reconcile order and customer counts against the old platform before switching the domain.

Who owns the code when an agency builds my software?

You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.

How secure is WordPress for a business website, really?

WordPress core is heavily audited and patched quickly; nearly every compromise traces back to an outdated plugin, a weak admin password, or bargain shared hosting. A hardened build keeps the plugin count low, enforces two-factor authentication on admin accounts, adds a web application firewall, and keeps backups you have actually test restored. For compliance, cookie consent and a privacy policy cover most GDPR duties, and a hosted payment gateway like Stripe keeps card data off your server entirely.

How long does it take to build a custom WordPress website from scratch?

Plan on 4 to 8 weeks for a custom-theme marketing site and 10 to 14 weeks for a WooCommerce store with CRM or ERP integrations. Across Digital Heroes projects, the biggest schedule variable is content: clients who deliver final copy and images before development starts launch around 3 weeks earlier than clients who send content page by page.

Will an app built for 10 users survive growing to 500?

Yes, if it is built on standard cloud infrastructure with a sound data model, because moving from 10 to 500 users is a hosting configuration change, not a rebuild. The scaling decisions that actually hurt are made early and invisibly: how the database is structured, how accounts and permissions are modeled, and whether background work is queued properly. Ask your agency how the system would handle ten times the load; the right answer is boring and specific, and a promise to cross that bridge later means you will pay for the bridge twice.

What should I prepare before contacting a software development agency?

A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.

How small can the first version of my software be and still be worth building?

One workflow, end to end, for one type of user: the single process that currently burns the most hours or loses the most money. In Digital Heroes delivery experience, first versions scoped to 6 to 10 weeks of build time ship, get used, and generate the feedback that makes version two obviously right, while 9-month first versions routinely launch with features nobody touches. Everything you cut from v1 gets cheaper to build later, because real usage reorders the roadmap for you.

Who can build a custom WordPress development system?

Digital Heroes builds custom WordPress development systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.

Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.

What makes Digital Heroes different from other WordPress development companies?

Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.

Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.

How can I check Digital Heroes is legitimate before getting in touch?

Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.

Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.

Keep reading
let's build

Build something worth launching.

A plan, a team, a timeline, within 24 hours. No decks, no discovery calls. Tell us what you're building and we'll come back with a real scope and a real number.

message us directly · we reply within one business day

mission briefing

Monthly dispatch

Playbooks, real build costs, and what we're shipping. One email a month. No fluff.

visit us

New York HQ

1140 Broadway, Suite 704 · New York, NY 10001

Get directions
Online now

Hey there 👋 How can we help you today?