Our own tools, with a defined implementation scope

Our own modules support specific website tasks: collecting an enquiry, choosing an appointment, receiving a job application or organising publishing. We match the scope to the workflow and existing environment.

Discuss an implementation

One need, connected modules
01 / Understand the need

STAR Conversion Flows

02 / Collect information

STAR Forms Builder

03 / Share materials

STAR Download Library

Connections are agreed for each implementation.

An example of tools working together around one need.

Enquiries ready for the next step

A form should collect what is needed to move forward, rather than every possible detail. For an RFQ journey we plan context, questions, a summary and a way to revise answers. STAR Conversion Flows guides the journey; STAR Forms Builder handles fields and storage according to the configuration. Questions follow the prepared scenario and the user’s answers.

Explore the scope: RFQ solution.

Bookings and calendars

For bookings we define services, providers, availability and confirmation rules. We can configure an agreed scope using STAR Appointments. A request, confirmation and notification are different events. Payments, SMS and connections to other calendars require an identified provider and separate checks.

Explore the scope: WordPress modules.

Careers and application handling

A careers section can connect vacancies with an application form and access for authorised staff. We agree fields, recipients, messages and retention. This is not a complete applicant tracking system, automatic candidate assessment or a hiring decision.

Explore the scope: WordPress modules.

Catalogues, documents and publishing

Modules can organise specifications, filters, downloads and content editing. For a portal we define categories, events, search and moderation. The source, draft and approval remain distinct editorial stages. A public download library is not automatically a private document repository.

Explore the scope: Business software.

From a module feature to an implementation

We first establish where data originates, who owns it and which existing functions must remain. We then agree the module, configuration and any extension. Each implementation has its own list of functions and dependencies, matched to the business’s needs.

The result is an agreed, versioned scope with configuration, guidance and update arrangements. A list of planned features is not a list of accepted features.

What to establish before work starts

Prepare the objective, a description of your existing website and the functions you need. Identify roles, enquiry recipients, retention rules and information that may be public. Acceptance covers the whole user journey, validation, errors and permissions. For submissions, storage, notification and receipt are checked separately. Activating a module does not complete these checks.

Solutions and implementations

Next step

Describe the user’s task and the functions that must remain. This will help define the implementation scope.

Discuss an implementation

Have a quick question? Get in touch.