Confidential B2B travel operations project
From scattered records
to connected work.
I designed and implemented a connected digital workflow for a destination management company—bringing data, proposals, invoicing and reporting into one system a small team could manage.
Explore the systemCover placeholder for a proposal, invoice review and reporting composition. Recreated interfaces will use demo data.
A limited public view of an ongoing engagement. Interface visuals are labelled placeholders. Detailed workflows and live business information remain confidential.
01 / The challenge
Complex operations.
A small team.
Scattered information, repetitive manual work and inconsistent proposals made everyday tasks harder. The main platform also did not support the company’s required German invoice format and process.
- Scattered records
- Manual proposal edits
- Separate documents
- Disconnected reporting
Clear records. Reusable content.
Connected steps.
Handle complex travel information.
Keep everyday work simple.
02 / What I designed
Four parts.
Designed to work together.
The design connected a reliable data foundation to the documents and views the team needed day to day.
01 / Data foundation
Structure the information.
Make it reusable.
I helped organise more than 3,000 operational records into a consistent structure for the new CRM and its connected workflows. This gave the team a reliable starting point for proposals and the steps that followed.
- Hotels
- Activities
- Transport
- Restaurants
- Clients
Screenshot placeholder for a structured record view. The future image will use dummy suppliers and service categories.
02 / Dynamic proposals
Adapt the content.
Keep the experience consistent.
I designed reusable, responsive HTML templates powered by variable data. Dates, travellers, accommodation, transport and activities could change for each proposal while the visual and content structure stayed consistent.
Reusable content + project variables → a tailored proposal.
Mockup placeholder for desktop and mobile proposal views. “Berlin Cultural Programme” is a demo title, not a live client project.
03 / Custom invoicing
Bridge the platform gap.
Keep review in the workflow.
The platform’s invoice process did not fit the company’s needs. I designed an API-connected workflow for structured review, controlled finalization and consistent document generation in the company’s required German format.
- Review
- Finalize
- Generate document
A public overview. Internal validation rules and financial controls are kept private.
Mockup placeholder for the review interface. Invoice numbers, client details and totals will be recreated with demo data.
04 / Financial reporting
Make the information useful.
Keep the view focused.
I created reporting views that turned operational data into clear financial information. The interface prioritised quick review, simple navigation and long-term maintainability for a non-technical team.
The right information for the task, without overwhelming the people using it.
Dashboard placeholder for five summary cards and an invoice table. Any future values will be explicitly labelled illustrative data.
03 / Simplified system flow
One thread through
the entire workflow.
The team moves from structured operational data to proposals, reviewed invoices and financial reporting within one connected setup.
- 01
Structured data
Organise the records the team works with.
- 02
Dynamic proposal
Bring reusable content into a tailored proposal.
- 03
Client approval
Agree the project with the client.
- 04
Invoice review
Review the document before finalization.
- 05
Finalization
Generate the final invoice document.
- 06
Reporting
Make financial information available to the team.
04 / The outcome
Less repetition.
A more consistent way to work.
The completed setup connects data, proposals, invoicing and reporting. Reusable, variable-driven templates reduced proposal generation time by 50%.
- Less time preparing proposals
- 50%
- Operational records structured
- 3,000+
Tested with the team
From setup to handover.
I tested real scenarios with the project manager and CEO, then prepared documentation and team training. The setup phase is complete; the client engagement is ongoing.
My contribution
Strategy through implementation.
I led the workflow audit, system architecture, UX, proposal templates, invoice and reporting implementation, testing and training.
Shreyas supported data migration. I used Codex as a development copilot and retained responsibility for system logic, design decisions, validation and final implementation.
He is able to translate complex operational requirements into clear, user-friendly and visually consistent solutions.
A closer look
The public story.
The details, in private.
Explore the design decisions, recreated interfaces and technical approach in a private online walkthrough.
Arrange a time by email.