Role: Design Manager (UX | UI) — design and front-end build, under Rohit's direction Duration: 12 weeks (ongoing) Platform: Equisoft RFX (web application)
Add: hero/cover image of the RFX product — ideally the review canvas or dashboard.
RFP teams at large financial firms spend weeks answering the same security questionnaires over and over. A single enterprise RFP can run 400–800 questions, and teams copy-paste from old Word files, Excel sheets, and SharePoint folders. The institutional knowledge exists — it's just scattered and unsearchable.
Equisoft RFX automates this. Clients upload an RFP, the system drafts answers by retrieving the closest past responses, and reviewers edit, approve, and export.
Core issues:
I worked with Kiara, Mark, and Ben on the Equisoft US team’s side to understand how their teams actually run a response cycle. Most of what shaped the product came out of these conversations.
| Stakeholder | Role | Insight |
|---|---|---|
| Kiara | RFP Lead | Half her week goes to chasing SMEs for answers the team has already written. |
| Mark | Security Officer | Every questionnaire repeats the same 200 questions in a slightly different format. |
| Ben | Pre-Sales | By the time the draft reaches him, he has 2 days to review 600 answers. |
Competitive scan. I looked at Responsive, Loopio, Conveyor, and AutoRFP. They all treat this as a search problem. The gap was reasoning — retrieving the right past answer, understanding the nuance of the new question, and generating a grounded response with citations.
Workflow audit. I sat with two response cycles end to end. Three things stood out: