Case Study

Designing Aidoos' AI Proposal Flow

From a single line of text to a signed, priced proposal. Every screen in between exists because a screen before it was cut.

Role

Product Designer/Design engineer

Product Context

Aidoos builds software for companies without them having to hire a team. A client describes what they need, and Aidoos assembles a Virtual Delivery Center: certified specialists plus AI agents who run the build end to end. Clients pay for defined outcomes rather than headcount or hours.

Company

Aidoos

Focus

Intake

Proposal

Pricing

Why this flow matters

A client's first real interaction with us is an AI-generated proposal, built from a few sentences they type, with no sales call in between. That makes this flow the single highest-stakes surface we own: it either earns enough trust for someone to hand over their email, or it quietly loses them.

Everything below is a decision I made to close that gap, roughly in the order I made it.

Decision 01

Type right there

What used to happen

You landed on the homepage, clicked, and a modal opened just to ask what you wanted. Two screens before you could type a word, each click is a friction point, drop off rate was higher.

Before

The previous homepage, a generic agency-style hero with no chat input in it
The old homepage: no chat input on it
The modal that used to open before someone could describe their project
The modal it opened after clicking ChatGPT for Work

After

The chat input sits in the hero. You land, you type right there.

AiDOOS
VDC
Pricing
About
Resources
Tools
For Talent
RAMP
Login
Free Trial
AI-Native Virtual Delivery Center.
Describe a project. Your VDC assembles
RAMP certified
talent and AI agents,
runs delivery end to end, and bills by outcome. Not headcount, not hours.
Describe a project
Plan my project
SAP ECC to S4/HANA migration
5 RAMP-certified backend engineers
No commitment · No sales call · See your team & scope before you pay

Decision 02

Show them you're actually reading it

The next screen is a short one that narrates what the system is doing with what they wrote: reading the brief, pulling out modules, estimating time. Not a spinner. The first proof their words went somewhere, because they might be skeptical if it is just a template or an actual engine

The actual screen: reading, then narrating what it found.

Decision 03: the single most important screen

Understanding, not a form

The next screen is where that trust is won or lost. Earlier, it used to generate the proposal with just the typed input.. a 100 char input is not enough to build a business plan, we needed more context.. This screen gets that context after making sure it provides value before asking, zoom in and out to read the thought behind each section...

Loading board
Scroll or drag inside the board to explore each callout.

Decision 04

A page, not a modal

The next screen is finally the proposal... It used to come as a modal but modal is for a decision you make and dismiss. A proposal is a document you read. So I moved it to its own page, with its own URL, and gave the sections a real order. The page is capped at a fixed width too, easier for the eye to read just like medium articles

Loading board
Zoomed out on purpose: this is the ordering argument, not the copy.

After the proposal is accepted

Once a client says yes, the team is matched, the SOW is signed, the wallet is funded, and the project goes live in its workspace.

Project formation: the matched team of four experts and three AI agents, with a stepper at SOW signing and a button to proceed
01 Sign the Statement of Work
The fund-your-wallet drawer: a progress bar toward the 48 DUs the project needs, and three DU packs with the minimum to start marked
02 Fund the wallet
The project workspace board: tasks across Backlog, To Do, In Progress, In Review and Done, each with DUs, priority and due date
03 Run the project from the workspace

21 screens in the full flow, desktop and mobile.

See them all in Paper
Get Started

Let's build something worth shipping

Pick a time below. No back-and-forth required.