Caledonian Tourers
Scottish campervan and motorhome hire website with SEO-focused destination and hire content.
Explore Caledonian TourersApp development
If your bookings live in one diary, customer details in another system and job updates in a string of messages, an app may help bring the work together. BMR Digital works with Dundee businesses from Bankfoot, Perthshire, starting with the task you need to make simpler.
In short
BMR Digital builds custom web apps for bookings, staff diaries, job cards, quotes and customer records. We agree the features, ownership, ongoing costs and a fixed build quote in writing. Payments, reminders and AI answering are options to scope, not features automatically included in every app.
These portfolio projects show different kinds of digital work. They are not Dundee client claims or proof that every proposed app feature has already been delivered.
Scottish campervan and motorhome hire website with SEO-focused destination and hire content.
Explore Caledonian TourersSame-day UK computer help: remote support, expert answers and an AI diagnosis tool.
Explore IT AdviseA useful brief describes what happens now. Who takes an enquiry, where is it recorded, who confirms the job and how does the customer hear back? Bring an example with personal details removed. A missed handover or repeated bit of typing is a better starting point than asking for an app that does everything.
For a Dundee team working across several jobs, the first version might be a shared diary and a job record staff can update from a phone. For an appointment business, it might be a booking request that the owner confirms. These are different workflows: taking a request does not mean promising a slot is available or a booking is confirmed.
An enquiry form can collect a preferred date without committing your team to it. Instant booking needs more: accurate availability, staff or equipment capacity, travel allowances, cancellation rules and a way to handle two people selecting the same slot. We decide which approach fits before designing the screens.
Deposits and automated confirmations can be included when the payment and messaging services support your requirements. Their charges and setup are separate things to agree. A failed payment must not look like a paid booking, and a failed notification needs a visible status so somebody can follow up. Automation can reduce repetitive work, but it cannot guarantee that every enquiry becomes a customer.
A job-management app can bring together the customer's request, an agreed quote, assigned staff, progress notes and completion details. A garage might need vehicle history and job photographs; a trade team might need site notes and access instructions. These are examples of possible workflows, not claims about named Dundee clients or systems we have delivered for them.
If your team also covers Broughty Ferry or Angus, describe how you allow for travelling between jobs. An address field alone does not make a workable schedule. The app can use agreed areas or travel allowances, while unusual jobs remain subject to a manual decision. You should be able to see who changed a booking and avoid exposing customer details to staff who do not need them.
Check the tools you already pay for before commissioning something new. An established booking service may already handle your appointments well. If the problem is an unclear website or staff not using the same diary, changing the process could be cheaper than replacing the software.
Custom work is worth discussing when an important step cannot be handled by your current tools, when information is repeatedly copied between systems, or when a customer portal needs a particular approval process. Compare the build and running costs with the work it would replace. We do not assume a custom app will save money simply because it has fewer subscriptions.
App development is quoted individually. Before you commit, the written scope should name the screens, user roles, integrations and first-release features. Hosting, email, text messages, payment processing and any AI service can carry ongoing charges. Those need to be explained alongside the build price, rather than appearing after launch.
A focused app may take two to four weeks once the scope and required material are agreed, but that is an estimate rather than a guaranteed deadline. Data migration, provider approval and more complex permissions can change the schedule. Larger systems should be divided into useful stages. If you request extra work, its price and effect on delivery are agreed before it is added.
Our usual approach is a web app that opens in a browser on a phone, tablet or computer. A suitable progressive web app can also be added to the home screen. That is not the same as a native App Store or Google Play app, and device features need checking against the actual phones your staff use.
Offline work is not automatic. If staff need to record notes without a connection, we must agree which information can be stored on the device, when it is synchronised and what happens if two people change the same job. Payments and live availability normally require a connection. We test the agreed workflow rather than promising that every feature works everywhere.
AI chat or answering can help collect an initial request, but it needs boundaries. Decide which questions it may answer, what details it should ask for and when a person must take over. It should not invent a price, confirm work outside your availability or present uncertain information as a decision from your business.
Telephone answering depends on the chosen provider and its connection to your existing number. Website chat is a different setup. We check the options and running costs during scoping. You still need a way to review captured enquiries, correct mistakes and contact the customer; an automatic acknowledgement is not the same as a human reply.
The handover should explain the code you own, how you access your records and any third-party software or services the app relies on. Customer information must be handled according to your responsibilities, not treated as something a software supplier owns. Agree export formats, staff access, retention and backup arrangements before sensitive data is imported.
Before launch, test the complete job with realistic, non-sensitive examples: submit a request, review it as staff, change its status and check what the customer sees. Also test rejected inputs and failed notifications. We explain the agreed workflow and support arrangements in plain English. Later changes are quoted separately; maintenance and third-party charges need an explicit agreement.
Booking requests and agreed appointment workflows
Shared diaries, job cards and progress tracking
Quotes, invoices and customer records
Staff access and owner dashboards
Hire inventory and availability workflows
Optional payment, reminder and AI integrations
Written scope and fixed build quote before work starts
Agreed device support and testing
Named user roles and access requirements
Ownership and data export explained in the handover
Third-party costs and integration requirements identified
Training and agreed aftercare arrangements
Need the enquiries as well as the system? We also do website design in Dundee and SEO in Dundee. Any connection between your website and app is checked and agreed during scoping.
For the full picture of what these systems can do, see business systems and apps, rental and booking apps and our pricing.
Yes. BMR Digital is based in Bankfoot, Perthshire and works with Dundee businesses remotely. Send your workflow through the enquiry form; if a call would help, request a callback and we will confirm a suitable time.
App work is quote-only. We agree a fixed build price after understanding the features, integrations and user roles. Hosting and provider charges are explained separately. Website package prices are not app-development prices.
AI answering may be possible with a suitable provider and connection to your phone service. We check that before quoting. It can collect details within agreed boundaries, with a human handover; it does not guarantee every call will be resolved.
A focused first version may take two to four weeks after scope and material are agreed. The actual schedule depends on the requirements and any provider approvals. Larger systems are planned in stages.
A web app can work through the browser on both. Home-screen installation, offline features and device access depend on the agreed implementation and supported devices. Native store distribution is a separate requirement to assess.
Your ownership and export arrangements are set out in the agreement and handover. We explain any third-party dependencies and charges rather than implying that owning the code removes every ongoing cost.
Describe the part of the week that eats your hours. We'll tell you straight whether an app is worth it — and what it would cost.
We are based in Bankfoot, so Dundee is close enough to meet in person when a project needs it, and most of the work happens remotely in between. The apps we build for businesses in and around Dundee are practical ones: booking and diary systems for trades, customer portals, job tracking for small teams, rental and hire management, and internal tools that replace a pile of spreadsheets. We are not a large studio and we do not pretend to be; you deal with the person building it.
The first conversation is about the job the app has to do. Who will use it, on what device, and what happens today without it? From there we usually suggest a small first version that solves the biggest problem, so you can use it with real customers before spending more. Pricing for app work is by quote, because a simple booking tool and a multi-user management system are very different jobs. Send a short description through the enquiry form and we will come back with honest questions and a sensible next step.