THE PROBLEM
Turning an RFP into a first draft takes weeks.
The opportunity often arrives late, and the clock is already running when it lands.
01
RFP arrives late
Sales receives it with days, not weeks, to respond.
02
Handed down the line
Passed from service line to service line for input.
03
Everyone researches alone
Each lead blocks time and starts from scratch.
04
Weeks disappear
A first draft is ready only after calendars align.
WHY IT COSTS US
Every RFP fans out across service lines, then waits on calendars.
The hand-off chain
Client Services receives the RFP
Software engineering line
Data and analytics line
UX-CX design line
What it costs
Duplicated effort
Each line researches the same RFP independently.
Scheduling drag
Progress stalls until everyone finds shared time.
Late, uneven base
The first draft is inconsistent and arrives near the deadline.
THE SHIFT
DesignRise flips the order of operations.
The design base is ready before the first meeting.
Instead of people fanning out to research, one AI augmented pipeline delivers the base, so the first conversation starts from real artifacts instead of a blank page.
HOW IT WORKS
From a public RFP to a bid-ready base in about 100 minutes.
1
Scan
Scout finds and scores live public RFPs.
2
Brief
One click turns a match into a live brief.
3
Research
Personas, journeys, IA, discovery questions.
4
Design
Figma Token-bound screens and a working prototype.
5
Draft
A branded Apexon proposal draft in Word, PPT, and code to build on.
Runs headless through a local bridge, writing real artifacts into Figma, FigJam, Powerpoint and Word.
PIPELINE LANDSCAPE
The whole system on one board.
WHAT YOU GET
One run delivers four artifacts to build on, not a slide of promises.
01
Research board
FigJam: RFP summary, personas, journeys, IA, and the discovery questions to ask.
02
Figma Design screens
Figma: token-bound concept screens drawn from a real component system.
03
Working prototype
A self-contained, clickable HTML walkthrough of the proposed direction.
04
Proposal draft and PPT
A branded Word starting point with every assumption flagged, for the team to refine.
PROOF: A REAL RUN
A live county RFP, scored and built end to end.
Sourced
Scout found a live municipal website redesign RFP on a public portal and scored its fit.
Verified
The link was checked against the issuer’s own document, and a false deadline was caught automatically.
Drafted
Research board, prototype, and a branded Apexon proposal draft, generated in one run for the team to refine.
Generated Apexon proposal draft, cover page. Marked draft, not for submission.
WHY IT IS TRUSTWORTHY
AI enabled, not AI generated. Every assumption is flagged.
Real components, bound tokens
Designs use the actual design system, with no invented variants.
Honest result states
Runs report ok, partial, or failed, never a fabricated success.
Assumptions ledger
Unknowns become explicit questions, and the proposal marks every assumption.
Client data walled off
Confidential client material is isolated and never leaks into new work.
THE PAYOFF
Weeks
~100 minutes
The same base that used to take weeks of coordinated effort, ready before the first working session. DesignRise builds the base. The team refines it and does the expert work from there.
Schedule a call for Live Demo
CREDIT AND ROLE
Built with a team, credited by name.
A system like this is not one person’s work, so here is who shaped it.
Lead UX and Agentic AI
Aniruddha Sainkar. I owned the UX and design side of DesignRise end to end.
Agent architecture
Adapted from Venu Shivalingappa’s SDLC prompt system.
Scope and direction
Richard Alvarez, Head of UX, and Umang Patel shaped where it went and where it stopped.
Runtime
Claude Code, by Anthropic. Node bridge, one definition file per agent.
Design file operations
Figma Console MCP, by TJ Pitre at Southleft. Open source, MIT licensed.
I am a product designer working on design systems, AI assisted design workflows, and the tooling between design and engineering. I am open to conversations about senior design work and mentoring.