Choosing your next step
Website or custom app: what does your Connemara business actually need?
The starting point
Start with the task that needs to become easier. Test existing tools before committing to a custom build.
If customers struggle to understand your services or make an enquiry, start with your website. If staff spend their day copying information, chasing updates or reconciling records, investigate the workflow behind it. Test existing software before commissioning a custom app.
The right investment depends on where the work gets stuck. A better website, a booking service and an internal application can serve different parts of the same business. You do not have to commission them all together.
For a Connemara owner or manager weighing up the next project, the useful starting question is: which task should become easier, and for whom?
Start with a task you can demonstrate
Bring an example to the first conversation: an enquiry that needed several follow-up calls, a booking entered in two places, or a report someone assembles manually each Friday. Remove personal or confidential details before sharing it.
Write down who starts the task, what information they need and what counts as finished. Then identify the obstacle. Is information missing? Does nobody own the next step? Or do the available tools genuinely prevent people from completing the work?
An unclear responsibility may need a process change. A confusing service page may need better writing and navigation. Neither automatically justifies a new application.
Use this table as a starting point for discussion, rather than a technical specification:
Swipe or scroll the table to see all columns →
| What is getting in the way? | Investigate first | What would justify a larger project? |
|---|---|---|
| Customers cannot understand the offer or find how to enquire. | Improve the website’s content, navigation and contact route. | A wider redesign if the existing structure cannot support those changes. |
| Bookings, payments or reminders take too much manual handling. | Trial an existing product against your actual booking process. | Important requirements remain unmet after configuration. |
| Staff repeatedly copy information between systems. | Check exports, supported connections and process ownership. | A custom connection or application solves a demonstrated gap. |
| Several people need to record, review and approve work. | Compare existing workflow tools with a small custom web-app proposal. | Required permissions or review steps cannot be handled sensibly by existing tools. |
| People must work on phones or without a connection. | Test the required tasks on the intended devices. | An installed app demonstrably meets requirements the browser approach cannot. |
A website improvement can be a complete project
If the main problem is attracting suitable enquiries, define a useful customer journey: understand the service, judge whether it fits, and take the next step.
That might mean clearer service pages, relevant examples and an enquiry form asking the right questions. It does not necessarily require customer accounts or a new booking system.
Ask someone unfamiliar with the business to complete that journey on a phone. Check whether they can explain what you offer and what happens after submitting the form.
Include accessibility in that review. W3C’s guidance explains that properly associated form labels help assistive technology identify each field and help people understand its purpose. 1
Specify the practical outcome: an enquiry that reaches the right person with enough information to respond. Agree how it will be tested before considering the work finished.
Give existing software a fair trial
Before paying to build a booking or administration tool, run a realistic task through an existing product. Include an awkward case: a cancellation, a changed attendee or a booking requiring approval.
Assess the whole task, including what staff do outside the software. A convincing demonstration should show your process from beginning to end, rather than a selection of attractive screens.
If two products need to exchange information, ask for confirmation of the specific connection. What data can move, in which direction, how often and under which subscription? Who investigates when it fails? Treat an unverified integration as an open question in the proposal.
A custom application becomes worth considering when those trials reveal a meaningful gap. If a modest change to the process makes an existing tool suitable, keep that option on the table.
Working on a phone does not settle the app question
A web application runs through a browser. Some can also be installed with an app icon and opened in a standalone window. Installation support varies by browser and platform; being installable does not itself establish that the application works offline. 2
For field work, ask for a demonstration on the phones your team will use. If offline recording matters, test losing the connection halfway through a task, closing and reopening the app, and sending the saved work later.
Make the required behaviour explicit: what can be viewed, what can be saved and how staff know the office has received it. Compare browser and installed approaches against those requirements, including updates and support.
A hypothetical example: a training business
Consider a fictional first-aid training business in Connemara. Customers need course information and booking confirmation. The coordinator needs an attendee list; instructors need to record attendance. This is a training-administration example, not a clinical-record system or a Féinics client case study.
A sensible first brief could be:
Customers should find suitable courses and book through an established booking service. The coordinator should manage bookings in one place and give instructors the attendance information they need. Before proposing custom software, demonstrate cancellations, attendee changes and attendance export using sample data.
For the first release, prioritise that complete journey. Defer a separate customer app, loyalty scheme or management dashboard unless there is a clear need.
If the trial reveals an attendance-review process the booking service cannot support, investigate that specific gap. There may be a case for a small staff tool while retaining the booking service.
Compare the commitment after launch
Ask each supplier to separate setup costs from recurring charges, maintenance and optional changes. Compare proposals over the same period and using the same assumptions about users, bookings or storage.
Agree who controls the domain and service accounts, what rights you receive to custom code, how records can be exported and what another supplier would need to take over. Put these answers in the scope or contract.
Data handling belongs in the design discussion. Ireland’s Data Protection Commission explains that privacy should be considered from the outset and that only data necessary for each processing purpose should be collected. 3 For your brief, identify the information each task needs, who may access it and how long it should be retained.
Also ask how recovery works. The National Cyber Security Centre distinguishes cloud storage from backups that can restore information after an incident. 4 Ask what is backed up, who tests restoration and what the recovery arrangements cover.
Bring the decision back to the original task. Commission a first release with a clear boundary, an owner and a way to judge whether it works.
Have a website or workflow that is making work harder than it needs to be? Discuss your website or app requirements with Féinics Engineering, starting with the task you want to improve.
References
- W3C Web Accessibility Initiative. Labeling Controls. Updated 13 May 2024.
- MDN contributors, MDN Web Docs. Making PWAs installable. Last modified 6 October 2026.
- Data Protection Commission, Ireland. Data protection by Design and by Default. No publication or update date displayed; accessed 13 October 2026.
- National Cyber Security Centre, Ireland, SME CORE. 5. Back-up your information. No publication or update date displayed; accessed 13 October 2026.
All references opened and reviewed on 13 October 2026.