Website, web app or existing software?.

Describe the task before choosing the technology.

Write out what happens today, from the first request to the completed job. Note who enters information, who checks it, where it is copied and where someone waits for a reply. Identify the specific step that causes difficulty.

For example, a Pembrokeshire business might need customers to submit a booking enquiry. Another might need staff to approve availability, collect documents and keep customers informed. The first may need a clear website and an existing booking service; the second needs a closer look at the workflow.

These are examples for planning, not a reason to commission custom software before checking existing options.

Compare the options against the same requirement.

Many projects combine a public website with another system. Choose each part for the job it needs to do.

Try existing products with real examples.

Use a representative task during a trial or demonstration. Include an ordinary case and an awkward one, such as a cancellation, missing information or a change requiring approval. A feature list cannot show whether the people doing the work can use the process comfortably.

Ask which subscription includes the required functions and how charges change with staff, customers, storage or usage. Check whether the information you need can be exported in a useful form. Ask about the specific systems you use rather than accepting a general promise of integration.

• Can each person see and change only the information they need?
• Does the process work on the devices your users actually use?
• What happens when a notification or connection fails?
• Can you leave the service with the records you need?

Give a custom build a clear reason to exist.

List the requirements that suitable products cannot meet and explain their effect on the business. Estimate the time, repeated work or errors involved using your own records. Compare that evidence with development, training and ongoing running costs.

Define a small first release around one complete useful task. Specify the starting information, the people involved, the actions they take and the result they should receive. A prototype can help test understanding before the full application is built.

Agree how you will check the result. For example, an authorised staff member should be able to review a request, record a decision and make the correct information available to the customer.

Plan who will look after it.

Include hosting, backups, support, software dependencies and future changes in the decision. Record who controls the accounts and data, who approves access and who responds when something stops working. Clarify which responsibilities stay with your business.

The right answer may be improving the process, configuring an existing tool or connecting services you already have. Custom development should follow a clear need and an affordable plan for keeping the application useful.

Start with the process you want to improve.

Select Pembs offers a free initial consultation for Pembrokeshire businesses considering websites, web applications or software choices. Describe the task and where it becomes difficult. Any detailed assessment, specification or development is scoped and priced before work begins.

Help with your next step.

Select Pembs is based in the heart of Pembrokeshire. We can discuss your situation in a free initial consultation, whether you are planning a project with us or want advice before choosing another supplier.