Automating Budgeting Workflows with AI

Capstone Project

— SEP 2025 - MAY 2026 —

OVERVIEW

OVERVIEW

At a Glance

At a Glance

PFF, LLC is a consulting firm that develops tools to help nonprofits, local governments, and small agencies manage their budgeting more effectively. For their emergency management clients, we redesigned InCEP, a legacy budget planning platform, into Treasora, an AI-assisted system that streamlines how mission assignments, cost estimates, and transactions move through a multi-role approval chain.

8 months

My Role:

Product designer

Team:

Team of 5

Results

Results

4.8 / 5
6 users rated the experience highly in usability testing

~ 10%
error rate across core workflows, as seen from usability tests

100+
high-fidelity screens delivered,
across desktop and mobile

6
journey maps delivered, covering the most critical workflows

Problem

Problem

Imagine you're a financial analyst during a hurricane response. You need to create a Mission Assignment so emergency work can begin fast…

You manually transcribe details from the emergency management document, hoping you've entered everything correctly. You submit it for approval and wait, with no visibility into where it sits in the queue, who's reviewing it, or when work can actually start.

You manually transcribe details from the emergency management document, hoping you've entered everything correctly. You submit it for approval and wait, with no visibility into where it sits in the queue, who's reviewing it, or when work can actually start.

InCEP Platform

Manual data entry slows workflows

Complex approval processes

No visibility into approval status

Instead, you're stuck in InCEP

Timeline

Timeline

For this year-long project, I led end-to-end user research efforts, championing a user-centered design process through the creation of user personas, user stories, and "How Might We" statements. I co-led the development of a comprehensive design system from scratch and also played an active role in usability testing, client presentations, and iterative design refinements.

For this year-long project, I led end-to-end user research efforts, championing a user-centered design process through the creation of user personas, user stories, and "How Might We" statements. I co-led the development of a comprehensive design system from scratch and also played an active role in usability testing, client presentations, and iterative design refinements.

RESEARCH

We started Sprint 1 by auditing the existing InCEP platform and analyzing competitors to understand where InCEP falls short and where the market already does better.

We started Sprint 1 by auditing the existing InCEP platform and analyzing competitors to understand where InCEP falls short and where the market already does better.

Competitor's Analysis

Some insights include:

  1. There is an opportunity to eliminate the manual burden of the legacy InCEP platform rather than simply adding an AI layer on top.


  1. If the tool requires extensive training, it will face adoption resistance.


  1. The strongest dashboard patterns share top-level KPIs at a glance with drill-down detail below.

Mapping InCEP Workflows

Some insights include:

  1. Emergency financial workflows are structured around three core entities: Mission Assignment (MA), Cost Estimate (CE), and Transaction.


  1. Cost estimates define how funding is allocated and must be approved before any spending can occur.


  1. Approval is embedded throughout the workflow, governing both funding decisions and actual spending.

Understanding User Needs

We planned to conduct primary interviews with emergency management staff, but a federal shutdown during our research phase made government employees inaccessible. Instead, we worked from PFF's existing interview notes from prior client engagements.

We planned to conduct primary interviews with emergency management staff, but a federal shutdown during our research phase made government employees inaccessible. Instead, we worked from PFF's existing interview notes from prior client engagements.

Financial Analyst

As a, Financial Analyst

As a, Financial Analyst

I want to, quickly create a Mission Assignment and/or Cost Estimate

I want to, quickly create a Mission Assignment and/or Cost Estimate

So that, emergency response work can start without delays

So that, emergency response work can start without delays

Requestor

As a, Requestor

As a, Requestor

I want to, record all transactions

I want to, record all transactions

So that, program managers and directors can track all purchases

So that, program managers and directors can track all purchases

Approver

As an, Approver

As an, Approver

I want to, spot the discrepancies or missing documents

I want to, spot the discrepancies or missing documents

So that, I can make approvals or return request confidently, providing accurate summaries.

So that, I can make approvals or return request confidently, providing accurate summaries.

Director

As a, Director

As a, Director

I want to, use the budget dashboard

I want to, use the budget dashboard

So that, I can oversee current spending and obligations on a daily basis

So that, I can oversee current spending and obligations on a daily basis

Organizational Workflow

The current platform treats a multi-role, time-sensitive workflow like a series of isolated forms with no intelligence, visibility, or continuity between steps.

IDEATE

How Might We

Faster Creation

How might we help financial analysts create mission assignments and estimate costs without manual data entry?

Informed Purchasing

How might we help requestors track spend against allocation before committing to a purchase?

Confident Approvals

How might we help approvers surface discrepancies and make confident decisions without line-by-line review?

Real-Time Oversight

How might we give directors real-time visibility into budget utilization across all mission assignments?

Design Decisions

Core Principle: AI informs, humans decide.

Emergency management funding is federally auditable. FEMA requires clear documentation trails showing who approved what, when, and why. If AI auto-approved a mission assignment or auto-submitted a cost estimate, there's no accountable human in the chain, and that breaks the audit trail the entire system depends on.

Emergency management funding is federally auditable. FEMA requires clear documentation trails showing who approved what, when, and why. If AI auto-approved a mission assignment or auto-submitted a cost estimate, there's no accountable human in the chain, and that breaks the audit trail the entire system depends on.

Information Architecture

Information Architecture

We defined a desktop-first MVP for validation and pitching, with mobile web as a secondary support for on-site scenarios. The MVP is structured into four core modules: Emergency Response, Finance, Approve, and Admin. The system reflects the financial workflow from planning (MA and CE) to execution (transactions).

We defined a desktop-first MVP for validation and pitching, with mobile web as a secondary support for on-site scenarios. The MVP is structured into four core modules: Emergency Response, Finance, Approve, and Admin. The system reflects the financial workflow from planning (MA and CE) to execution (transactions).

PROTOTYPE

Design Strategy: Focus, Iterate, and Scale

To manage the complexity of a multi-role financial system, we focused on key modules first and iterated from desktop wireframes to high-fidelity designs. This structured approach enabled faster feedback, clearer workflows, and scalable system development.

We made early sketches and wireframes to define core layouts and key workflows. We also explored multiple design directions for different interaction patterns and system structures.

Design System

We built a comprehensive design system from scratch in Figma with 85+ reusable components, including buttons, tables, navigation, and form elements, so that every screen across web and mobile inherited a shared visual language.

TEST

We tested the prototype with 6 participants deliberately recruited across a spectrum, from seasoned InCEP users to first-time users with no financial planning background. Testing focused on 4 tasks that mirror the full approval chain: create a Mission Assignment, create a Cost Estimate, approve the estimate, and create and approve a Transaction.

Key Insights

Discoverability & Clarity

Users struggled to understand key actions.

  • The “Create Cost Estimate” link is not obvious.

  • Terminology (CE, MA, funding lines) is confusing for new users.

AI Visibility

AI features were valuable but often missed.

  • AI Review is not prominent.

Trust & Control

Users were unsure how much to trust AI outputs.

  • Confusion around confidence score & data source.

  • Users wanted to see the “why” behind confidence scores.

The Approval Chain in Action

Financial Analyst

Create Mission Assignment

Instead of manually transcribing every field, the analyst uploads the source document and reviews what the system extracts.

Financial Analyst

Create Cost Estimate

For cost estimation, AI references similar past mission assignments and suggests funding line amounts.

Approver

Review submissions and approve/reject

AI generates a findings summary ranking every issue by severity.

Requestor

Create Transaction

For transactions, AI suggests spend plan lines and object class codes based on the expense description.

Director

Monitor spending and ensure compliance

The budget dashboard gives the director real-time visibility into spend across every mission.

REFLECTION

REFLECTION

This eight-month project with a real client, a real approval chain, and real constraints taught me more than any classroom project could. Here's what stayed with me:

  1. Building a design system from scratch taught me that the system isn't the components, but the decisions baked into them. Every token, spacing rule, or state variant is a decision you make once, so you never have to make it again.


  1. Designing for four users sharing one workflow is negotiation. Every screen had to serve the person using it without breaking the experience for the person who touches it next. The hardest design problems weren't visual; they were figuring out what the Approver needs to see that the Analyst didn't know to provide.


  1. AI is easiest to design when you stop asking "where can we add AI?" and start asking "where is a human doing work a machine should handle?" That reframe eliminated half our ideas and sharpened the rest. The features we cut were more important than the ones we kept.

Let's build the next one together!

Saumya Verma © 2018-2026 All Rights Reserved