abdulbasid / bagirei← Back to work

GAJIMARI TRAVELS & TOURS / CASE STUDY

Less admin.
More time for
the journey.

A website and custom staff system that connect customer enquiries to the team’s daily work. Built around the client’s requirements, and in active use.

WHAT NEEDED TO CHANGE

One enquiry.
A lot of work behind it.

Planning travel means gathering requirements, researching options, coordinating suppliers, preparing documents, and keeping the customer informed.

Gajimari handled that administration manually. The same information was needed in summaries, quotations, invoices, and correspondence. I built a connected system around the client’s process, so the team could reuse those details and keep responsibility clear.

01 / FOLLOW THE WORK

From “I need a trip”
to a request the team can handle.

Meet Amina, a fictional customer.
Select a step to see what happens.

STEP 01 / REQUEST

Amina tells the team what she needs.

Amina needs flights and accommodation for a business trip. The website explains the services, then guides her through the details the team needs to get started.

THE SOFTWARE

The guided form collects the travel requirements and contact details in a structured enquiry.

THE PEOPLE

Staff still clarify any missing details and help the customer choose the right service.

GAJIMARI / WORKFLOW01

New travel request

Customer
Amina · fictional example
Services
Flights + accommodation
Trip
Business travel
Next step
Submit request

Illustration of the workflow · fictional data
Not a screenshot of the staff system.

STEP 02 / CONFIRMATION

She knows her request has arrived.

After a successful submission, Amina sees confirmation, receives an acknowledgement email, and can download a branded brief with her enquiry reference.

THE SOFTWARE

Acknowledgement, reference generation, and the customer brief happen without someone preparing a separate receipt.

THE PEOPLE

The team follows up on the request itself. An acknowledgement confirms receipt; it does not confirm a booking.

GAJIMARI / WORKFLOW02

Request received

Reference
GJM-2026-000001 · sample
Email
Acknowledgement sent
Brief
Available after success
Booking
Not yet confirmed

Illustration of the workflow · fictional data
Not a screenshot of the staff system.

STEP 03 / OWNERSHIP

Someone takes responsibility.

The enquiry appears in the staff inbox. An employee claims it, so the rest of the team can see who is handling it. A super administrator can reassign it when needed.

THE SOFTWARE

The request, its status, and its owner are visible in the shared workspace.

THE PEOPLE

An employee reviews the details, contacts Amina, and coordinates the next steps.

GAJIMARI / WORKFLOW03

Enquiry workspace

Customer
Amina · sample
Owner
Travel adviser · sample role
Status
Being reviewed
Action
Clarify travel requirements

Illustration of the workflow · fictional data
Not a screenshot of the staff system.

STEP 04 / QUOTATION

The team prepares the options.

The employee researches suitable flights and accommodation, then prepares a quotation. Reusable communication templates provide a starting point for the reply.

THE SOFTWARE

Quotation tools and message templates reduce repeated document preparation and drafting.

THE PEOPLE

Staff choose suitable options, confirm supplier information, and tailor the offer to Amina’s needs.

GAJIMARI / WORKFLOW04

Quotation preparation

Request
Linked to the enquiry
Options
Prepared by the adviser
Message
Template, then personalised
Next step
Customer reviews the offer

Illustration of the workflow · fictional data
Not a screenshot of the staff system.

STEP 05 / INVOICE

Accepted details are used again.

When Amina accepts the quotation, staff can import the relevant information into an invoice instead of typing it all again.

THE SOFTWARE

Quotation-to-invoice reuse cuts down on repeated entry and keeps the documents connected.

THE PEOPLE

Staff check the invoice and handle the customer’s acceptance and payment arrangements.

GAJIMARI / WORKFLOW05

Invoice preparation

Source
Accepted quotation
Details
Imported, then checked
Document
Branded invoice
Next step
Staff arrange the journey

Illustration of the workflow · fictional data
Not a screenshot of the staff system.

STEP 06 / PROGRESS

Everyone can see where the work stands.

Staff continue making the arrangements and update the enquiry’s status. Management can view ownership, workload, and recent activity as the work moves toward completion.

THE SOFTWARE

Shared statuses, activity, and notifications make progress easier to follow.

THE PEOPLE

Staff arrange the trip, work with suppliers, and provide the personal service the customer needs.

GAJIMARI / WORKFLOW06

Team overview

Ownership
Visible to the team
Progress
Updated by staff
Workload
Available to management
Service
Delivered by the travel team

Illustration of the workflow · fictional data
Not a screenshot of the staff system.

The software handles repeated administration. People still choose travel options, work with suppliers, check documents, and look after the customer.

02 / BEFORE & AFTER

What changed
in the everyday work?

Choose a task to compare.

Request details

BEFORE

Staff collected and organised customer requirements manually.

NOW

A guided form captures the details and creates an enquiry.

Why it matters: Less time collecting the same basic information.

Acknowledgements

BEFORE

Someone prepared the initial acknowledgement.

NOW

The customer receives an automatic acknowledgement after a successful submission.

Why it matters: Customers get immediate reassurance that their request arrived.

Customer briefs

BEFORE

Request summaries were prepared separately.

NOW

Branded briefs are generated from the submitted information.

Why it matters: Less document preparation and a consistent reference for both sides.

Task ownership

BEFORE

Responsibility had to be coordinated outside the request.

NOW

Claiming and reassignment show who owns each enquiry.

Why it matters: Clear responsibility when several employees share the inbox.

Common messages

BEFORE

Staff repeatedly drafted similar messages.

NOW

Templates provide a starting point that staff can personalise.

Why it matters: Less repeated writing while keeping replies relevant.

Invoices

BEFORE

Quotation details were entered again for an invoice.

NOW

Relevant quotation information can be imported.

Why it matters: Less duplicate entry and fewer opportunities for typing mistakes.

Team progress

BEFORE

Management depended on individual progress updates.

NOW

Statuses, workload information, and recent activity provide a shared view.

Why it matters: Easier oversight without asking everyone for a separate update.

WHAT THAT MEANS FOR THE BUSINESS

01 / CUSTOMERS

An easier way to enquire.

A clear website explains the services and gives prospective customers a straightforward next step. Confirmation and a branded brief reassure them that their request arrived.

02 / TIME & COST

Less work done twice.

Automatic acknowledgements, generated briefs, reusable messages, and connected documents reduce repeated administration. That can save staff time and reduce the cost of handling each enquiry.

03 / SALES & GROWTH

A better chance to follow through.

Visible ownership and progress help the team handle enquiries consistently. That supports follow-up and gives the business a better foundation for turning requests into bookings.

These are the practical benefits of the system. Revenue growth, conversion rates, and hours saved have not been measured, so I don’t claim numerical improvements.

03 / BEHIND THE BUILD

The decisions
that made it work.

Developed through client requests, feedback, and testing. Open a detail to read more.

A website connected to the team’s work

A submission needed to become a request someone could act on. Connecting the public website to the staff inbox keeps the customer’s details and reference with the work, rather than leaving them in a separate contact form.

Clear ownership, with room to reassign

A shared inbox answers “what has arrived?” Claiming answers “who is handling it?” Super-administrator reassignment gives the team a way to change responsibility when necessary.

One brief format on both sides

Customer and staff briefs use the same document engine and enquiry reference. A downloadable customer brief is only available after the system accepts the submission, so it refers to a real enquiry.

Two interfaces for two different jobs

Customers need service information and a straightforward request process. Employees need requests, documents, ownership, and progress. Separate interfaces let each audience focus on its own work.

Refined through client requests and testing

The work developed around the client’s requirements. Testing and feedback shaped mobile behaviour, navigation, fixed interface elements, invitation redirects, document access, and quotation-to-invoice reuse.

What the full build includes

For customers

  • Service and company pages
  • Responsive, multi-step request form
  • Success and failure pages
  • Automatic acknowledgement emails
  • Branded briefs and enquiry references
  • Sitemap and Search Console setup

For the team

  • Enquiry inbox and status tracking
  • Claiming and administrator reassignment
  • Communication templates
  • Quotations and invoice preparation
  • Quotation-to-invoice import
  • Customer-brief downloads
  • Analytics, workload, and recent activity
  • Live updates and notifications
  • Staff invitations, roles, and deactivation
  • Individual staff profiles

HAVE A SIMILAR PROBLEM?

Which part of your work
keeps getting repeated?

Tell me how your business works, where time gets lost, and what you’d like to improve. We can work out what a website or custom software could help with.

Tell me about your business ↗