Reimagining contextual business travel management with an AI agent

Overview
In my previous role as a project manager at an ERP company, I learned how business travel management demanded significant effort, not only from employees who travel, but also from managers approving expenses and finance teams ensuring policy compliance. These processes often involved complex rules, contextual decisions, and exceptions. Leveraging AI’s ability to analyze data and understand context, I designed an AI agent to address these challenges. As an experiment, I used AI throughout the design process.
AI Agent
Figma Make
ChatGPT
Gemini
Project Type
Personal project
(as a part of AI agent bootcamp)
Timeline
Aug 2025 - Nov 2025 (Weekends)
Team
Myself
Tool
FigmaMake, ChatGPT, Gemini
Key Takeaway
AI accelerated research and exploration, but designing complex, consistent prototypes still required human judgment, critical thinking, and careful refinement.
Why Business Travel Management?

Curious how AI can improve nuanced work where traditional ERP systems fall short

As a project manager at my previous company, I led a client’s shift from paper-based travel expense reports to an ERP workflow. The experience revealed how nuanced and context-dependent expense management can be, with many decisions still handled manually. It sparked my curiosity about how AI agents could create smoother, more intelligent experiences by understanding context.

Approach

What if I used AI for the entire design process?

I was also curious about how AI could support the design process, especially in complex enterprise product design. In this project, I experimented with using AI at every stage.

Research
Perplexity
ChatGPT
Gemini
User research
Competitor research
Define goals
Explore opportunity
Ideate
ChatGPT
Gemini
Create user flow
Create scenario
Gemini
Create rough prototype
Prototype
Gemini
Create rough prototype
Figma Make
Mid-fi Prototyping
ChatGPT
Create sample script
Create sample data
Explore visual design
Evaluate
ChatGPT
Gemini
Get usability feedback
I also experimented with various tools such as MagicPattern, Claude and Lucidchart throughout the process.
Final design

Final design here

aaaa

Problem

Business travel management still requires nuanced human judgment and manual work

First, I researched typical business travel and expense workflows using AI. The process usually begins with trip planning and pre-approval, followed by post-trip expense submission, review, and reimbursement.

Expense management involves multiple stakeholders and context-dependent decisions. Travelers, approvers, and finance teams all face manual work, exceptions, and error risks, making the process fragmented and inefficient. Even with defined policies, many exceptional cases still rely on human judgment beyond what traditional systems can handle.

Challenges by Role
✈️ Traveler (Employees)
Policy-Compliant Trip Planning
Lack of policy clarity makes it hard to plan compliant trips.
Manual Reporting
Entering expenses manually is time-consuming and error-prone.
✅ Approvers (Managers)
Manual Review
Checking reports for accuracy and compliance takes time.
Context Judgment
Some exceptions require human flexibility and context awareness.
💰 Finance Team
Error & Fraud Risk
Manually detecting policy violations and errors is difficult.
System Limitation
Enterprise tools can’t handle context-based exceptions.
Research

Deep contextual support elevates AI agents beyond today’s competitors

I researched competitors using AI, reviewing strengths, weaknesses, features, and UI patterns across platforms such as Navan and Ramp to identify opportunities for an AI agent. This revealed that while competitors offer AI features, they still rely on rigid rules and task focused automation.

Opportunity
Context aware decision support
AI can interpret company policy, approval history, and contextual data such as calendar events to support travel planning and expense approvals. This enables personalized, low effort workflows and reduces approval work, especially in exceptional or flagged cases that require flexible judgment.
Competitor UI research
Product
Strength
Weakness
Navan
Modern UX. Strong AI agent for booking and real-time policy enforcement. Excellent mobile UX and fast automation for tasks.
Powerful but task focused AI with limited cross system context. Less flexible for highly complex or custom enterprise policies.
Ramp
Clean, simple UX. Strong automation for receipts, categorization, and real-time card policy enforcement. Clear spend visibility.
Card-centric. Minimal contextual interpretation. Weak support for complex approvals, multi-entity policies, or exception-heavy scenarios.
SAP Concur
Strong enterprise coverage with ERP integration and solid AI for receipts and basic anomaly detection. Good for large organizations.
Outdated UX. AI is not truly autonomous. Weak contextual understanding.
📝 AI Experiment Note
Viewing competitor enterprise products

AI has been especially helpful for enterprise product research, allowing me to efficiently gather screenshots and visuals that would otherwise be difficult to access without sign ups or direct inquiries. It is also useful to look at products from other sectors that offer similar features.

My Prompt Example:
• Gather screenshots of the approver interfaces from major expense management products, including Ramp, Navan, and SAP Concur.
• Gather screenshots of enterprise software where AI assistance and manual input are both available.
Goal

Reduce manual work in planning, reporting, and approvals while keeping policy compliance and a good employee experience, even in contextual cases ✈️

KPI
Metric
Target
Travel planning efficiency
Time spent on planning tasks for employees
Decrease
Approver workload reduction
Time spent on manual review steps through contextual interpretation and automated validation
Decrease
Policy compliance
analysis accuracy
Percentage of approval cases where the AI agent’s decisions align with human judgment
Near 100%
User satisfaction for AI agent
Perceived usefulness score of the AI agent’s assistance
High (4+ out of 5)
Agent Persona

AI agent as proactive partner

To begin, I defined the AI agent’s personality traits, voice and tone, and key behaviors needed to support users as an effective collaborator. These elements guided how the AI assisted users throughout the workflow.

🧠 Personality Traits
Proactive, trustworthy, insightful, and flexible
💬 Voice and Tone
Efficient, direct, professional, and calm
🤖 Key Behaviors
• Anticipates user needs
Identifies upcoming needs and assists with the next steps based on context, requiring less explicit instructions.
• Explains decisions clearly
Provides data based reasoning behind its insights and decisions.
• Helps resolve exception situations
When a policy conflict occurs, the agent does not leave the workflow entirely to the user or reject the request. Instead, it guides the user through an exception path so they can move forward with support.
• Confirms high stakes actions
Handles research and preparation, then presents irreversible steps like payment or submission for user approval.
Exploration

Defining core features and rough design direction

I first used Gemini and ChatGPT to outline rough features and workflows, then explored visual directions with Figma Make. This led me to define 4 key feature directions.

Feature 1
Compliant and flexible travel planning

Creates a personalized, policy compliant trip plan by checking rules, user intent, connected info like calendar and approval history, and external factors. It drafts travel options and adapts to exceptions.

Benefit

Reduces time spent navigating detailed policies, and makes trip planning faster.

Ver 1 Prototype (Originally in color, converted to grayscale in this image)
Feature 2
Assist expense report

Creates a policy aware expense report by auto capturing receipts, categorizing expenses, and running compliance checks. It fills missing information, drafts context based justifications, and guides the user through resolving flagged items.

Benefit

Reduces the manual work of interpreting policies, preparing reports, writing justifications.

Feature 3
Assist expense approval

Supports trip expense approvals by checking expenses and surfacing key insights such as flagged points. It recommends next steps based on context and relevant history.

Benefit

Managers and finance teams can focus on higher level judgment.

Feature 4
Intuitive company policy setting

Turns complex travel expense rules into clear settings by parsing policy documents and capturing soft operational nuances.

Benefit

Reduces admin effort for audit and finance and makes the system aligned with intended operations.

📝 AI Experiment Note
What's the role of AI prototyping?

As a former engineer, I was impressed by how quickly AI generated code. But in the early stage, the prototype distracted me from the core problem because it added unnecessary features and visual details. Combined with an unestablished IA, refining design felt overwhelming particularly for an complex enterprise workflow. I wanted to explore multiple UI options but it was hard with Figma Make.

The AI prototype was also not fully high-fi with inconsistent visual design. Yet, AI is inefficient for adjusting small details. But generating a working prototype in Figma Make and then returning to Figma  also feels like duplicated effort... These findings made me reflect on the role of an AI prototype in the process. I am still exploring the best design workflow.

✅ Strength
• Able to visualize rough ideas quickly
• Good for prototyping complex interactions
🚨 Weakness
• Hard to stay focused on the core problem
• Visual design consistency and refinement
• Difficult to ideate multiple options
Scope

Round 1 prototyping revealed the need to narrow the scope and define a focused scenario

The 1st iteration set the direction, but I needed to define more details on how the AI agent works. However, travel policies vary by company and business travel has many types exceptions, so covering everything at once was unrealistic. So, I made sample expense policy and scenario using ChatGPT as a starting point.

Company policy - with room for human judgment

The sample policy includes basic rules such as booking requirements, rate limits, and expense reporting steps. It also leaves room for human judgment or contextual decisions like these:

• "Reasonable and necessary expense"→ Case by case
• "Most cost effective without compromising safety or comfort"
• "Reimbursed if required for business purposes"
Scenario - with flagged items and user preferences

I created a realistic scenario that goes beyond the happy path and includes exceptions, flagged items, and user preferences, so I can think through how the AI agent should support these cases.

• Last minute booking for client driven need
• Price increases caused by external events
• Client entertainment meal
• Preferences of seat type, hotel brand, or location
• Abstract travel preferences (such as transport between meetings)

I also created an expense transaction list and sample receipts as a starting point for defining the ideal expense management workflow.

Workflow & Specification

AI agent as proactive partner

The workflow and specification is important to build an enterprise feature, and that part needs to be well-defined.

📝 AI Experiment Note
Prompting for generating workflow

I added the elements I needed for the workflow into the prompt so ChatGPT would return the right information. I also asked ChatGPT to review and refine the prompt.

My Prompt Example:
# Instruction
You are a UX designer creating an enterprise product. Based on the following requirement, generate a step-by-step user flow.

# Format
For each step in the flow, include:
- Overview: Short summary of the step
- Actor: Who performs this step (e.g. Employee, Manager, AI agent)
- Condition/ Action Trigger: When this step occurs
- Action: What the actor does (e.g. fills out form, clicks submit)
- Input: Data or choice referred
- Output: Data or documents produced
- Error Handling / Exception: What happens if something goes wrong

# Context
{{ Insert requirement and overview of feature, and scenario }}
Prototyping

Adding complex feature spec and fixing visual design consistency

The workflow and specification is important to build an enterprise feature, and that part needs to be well-defined.

📝 AI Experiment Note
Prompting for generating workflow

I added the elements I needed for the workflow into the prompt so ChatGPT would return the right information. I also asked ChatGPT to review and refine the prompt.

My Prompt Example:
# Instruction
You are a UX designer creating an enterprise product. Based on the following requirement, generate a step-by-step user flow.

# Format
For each step in the flow, include:
- Overview: Short summary of the step
- Actor: Who performs this step (e.g. Employee, Manager, AI agent)
- Condition/ Action Trigger: When this step occurs
- Action: What the actor does (e.g. fills out form, clicks submit)
- Input: Data or choice referred
- Output: Data or documents produced
- Error Handling / Exception: What happens if something goes wrong

# Context
{{ Insert requirement and overview of feature, and scenario }}
Prototype

aaa

aaa

📝 AI Experiment Note
Effective prompting after defining specifications

As a former engineer, I was impressed by how quickly AI generated code. But in the early stage, the prototype distracted me from the core problem because it added unnecessary features and visual details. Combined with an unestablished IA, refining design felt overwhelming particularly for an complex enterprise workflow. I wanted to explore multiple UI options but it was hard with Figma Make.

The AI prototype was also not fully high-fi with inconsistent visual design. Yet, AI is inefficient for adjusting small details. But generating a working prototype in Figma Make and then returning to Figma  also feels like duplicated effort... These findings made me reflect on the role of an AI prototype in the process. I am still exploring the best design workflow.

Prototype

Prototype

As a project manager at my previous company, I led a client’s shift from paper-based travel expense reports to an enterprise workflow. The experience revealed how nuanced and context-dependent expense management can be, with many decisions still handled manually. It sparked my curiosity about how AI agents could understand context to create smoother, smarter experiences.

Testing

Prototype

As a project manager at my previous company, I led a client’s shift from paper-based travel expense reports to an enterprise workflow. The experience revealed how nuanced and context-dependent expense management can be, with many decisions still handled manually. It sparked my curiosity about how AI agents could understand context to create smoother, smarter experiences.

Iteration

Prototype

As a project manager at my previous company, I led a client’s shift from paper-based travel expense reports to an enterprise workflow. The experience revealed how nuanced and context-dependent expense management can be, with many decisions still handled manually. It sparked my curiosity about how AI agents could understand context to create smoother, smarter experiences.

Final Design

Prototype

As a project manager at my previous company, I led a client’s shift from paper-based travel expense reports to an enterprise workflow. The experience revealed how nuanced and context-dependent expense management can be, with many decisions still handled manually. It sparked my curiosity about how AI agents could understand context to create smoother, smarter experiences.

Takeaway

AI can speed up design, but complex products still need human judgement and critical thinking

✅ AI helped me to...
Understand unfamiliar workflows
Gather competitor insights
Generate sample data and scenarios
🚨 I found it hard to…
Prototype complex features
Refine prototype details
Maintain visual consistency

AI helped me quickly understand user workflows and competitors, but prototyping complex features while maintaining consistency required extra prompting and refinement. I also learned the importance of critical thinking, as AI often adds unnecessary details. Moving forward, I want to explore how AI can best integrate into design workflows, whether for early exploration or refined handoff.

My Approach

What if I used AI for the entire design process?

I was curious about how AI could support the entire design process, especially in complex enterprise product design. In this project, I experimented with using AI at every stage, from research and ideation to prototyping and refinement.

📝 AI Experiment Note
What's the role of AI prototyping?

As a former software engineer, I was impressed by how quickly AI generated code. But in the early stage, the prototype distracted me from the core problem because it added unnecessary features and visual details (Maybe I should have explicitly asked for low-fi.). Combined with an unclear information architecture, design task felt overwhelming for an complex enterprise workflow. I also wanted to explore multiple UI options, not just the single direction that AI produced.

AI could create complex interactions like a drag and drop policy builder, but the information architecture and detailed specs are still left for designers to figure out.

However, the AI prototype was not fully high-fi. AI is also inefficient for adjusting small details (Fixing simple design through prompts takes 10+ seconds, while I can update it directly much faster). But generating a working prototype in Figma Make and then returning to Figma for the final spec feels like duplicated effort. These findings made me reflect on the role of an AI prototype in the process. I am still exploring the best design workflow.

✅ Strength
• Able to visualize rough ideas quickly
• Good for prototyping complex interactions
🚨 Weakness
• Hard to stay focused on the core problem
• Visual design consistency and refinement
• Difficult to ideate multiple options
Sample of a specification document we previously created in spreadsheets.
Our Team

Developing complex HR features without designers

Our team built custom ERP add-ons for a 20K-employee client to manage complex HR workflows. Since we didn’t have designers, solution consultants handled specifications. However, design was not well understood and was considered a relatively low priority.

AI helped me quickly understand target users’ workflows and competitors, but when it came to prototyping, I found it challenging to handle complex features, maintain visual consistency, and refine details, it often required extra prompting effort. I also realized the importance of critical thinking, since AI tends to add unnecessary details. Going forward, I want to explore how AI can best fit into a design team’s workflow, whether prototypes are more effective for early exploration or can be refined for direct handoff.

Engineers
Develop features
Solution Consultants
Communicate with clients to define specifications
Project Managers
Manage project progress
No Designers
Design was not treated as a distinct role
Problem

Inefficient design process slowed the project

We designed for a client’s complex internal workflow involving multiple user roles, many steps, numerous exceptional business rules, and client-specific jargon, which made the project especially challenging.

Multi-roles
Mult-steps
Exception Handling
Client Jargon
During Design Handoff

Confusing spreadsheet-based specification documents

We used spreadsheets to manage specifications, which often led to misunderstandings, extra work, and excessive communication around details like components to use, interaction and workflow.

Sample of a specification document we previously created in spreadsheets.
During Development

Feasibility issue found, taking time for redesign and approval

Because we used a component library, development feasibility and effort largely depended on the components available. Engineers could suggest improvements, but often too late in the process, requiring solution consultants to go back to clients for confirmation.

After Development

Change requests and missed considerations wasted development effort

After seeing the developed features, clients often noticed misunderstandings in the workflow or missing features and exception cases, which required us to rework the design and fix the implementation.

Goal

Enable a non-design team to design intuitive, feasible features that address client needs more efficiently

Strategy

Explored how to leverage design thinking for the team

As an engineer with a passion for design, I took on the challenge of solving this problem using design thinking. Due to project constraints, I needed to adapt the approach rather than follow every step. I discussed with the team to gather insights on what could improve efficiency the most and defined 3 key focus areas.

1

Visualize workflow

Visualize clients’ as-is and to-be processes to share common understandings and prevent overlooked considerations.
2

Document spec better

Show how features should work and look more clearly for both engineers and clients.
3

Fix early in the process

Reduce wasted effort by catching issues before development.
Solution

Here is our new design process

Based on the new strategy, I updated the design process. Here’s what the revised process looks like.

Improvement 1

Added workflow mapping step before design

Mapping the current and ideal workflows made it easier for clients and our team to align on the target flow. I researched common flowchart documentation methods and tools, adopted draw.io, and established a consistent format with simple flowchart rules.

🎯 Objectives
Align on each step and role between clients and our team
Facilitates discussion of the process without distraction from details
Clarify exception and error scenarios
Clarify input and output
🔨 Tool selection

I evaluated draw.io and Mermaid, focusing on how easily the team could learn and use the tool, and decided on draw.io.

draw.io
✅ Easy and intuitive for the team to learn
✅ Adaptable to complex workflows
👎 Requires manual work
Mermaid
✅ Reduce manual effort in creating visuals
👎 Steeper learning curve
👎 Charts become messy when workflows are complex
Improvement 2

Introduced prototyping and detailed specification documentation

I replaced the spreadsheet-based wireframes with Figma prototypes. Because the workflow we managed was highly complex, using Figma alone wasn’t enough to fully capture how the features should function. To address this, we complemented the prototypes with a text-based specification document that mapped the client’s requirements to the functionality of our add-on features.

🎯 Objectives
Reduce development inefficiencies caused by unclear specifications
Capture client requests and feedback on features early through high-fidelity prototypes
In the text-based specification document, each requirement was paired with its corresponding specification.
📢 Guiding adoption

Since our team didn’t have dedicated designers, I focused on simplifying design tasks to make the new process practical and sustainable. I leveraged existing frameworks and resources, and shared design knowledge through presentations and documentation.

Used Material Design

Reduced the cost of building a custom design system while maintaining design quality.

Adopted UI kit

Used the Vuetify UI kit to save time and stay aligned with pre-existing components.

Shared knowledge

Held presentations and created guides to introduce design knowledge to the team.
Improvement 3

Encouraged cross-functional discussions on feature design with engineers

I set up internal meetings before sharing designs with clients to ensure feasibility. These sessions provided opportunities for engineers to share technical limitations and for solution consultants to contribute their understanding of client workflows and requirements.

🎯 Objectives
Design collaboratively to create feasible, easy-to-develop solutions for clients’ needs
Help engineers better understand features
Result

Pilot testing confirmed the new process works

During pilot testing, we applied the new development process to design several new features, reducing communication time between developers and consultants by about 30 minutes per ticket. I left the company to pursue my master’s but would have continued improving and evaluating the process if I had stayed.

Next Step

I am curious how AI can even enhance the process

I learned how to make the design process practical and sustainable for a team of non-designers by leveraging existing frameworks, resources, and sharing design knowledge. This project took place in 2023, and if I were to revisit it today, I would explore incorporating AI tools to accelerate and enhance the process.