16Cloudera-to-Azure RFP — Architecture, Costing and Writing to Final Negotiation
Owned architecture, costing and writing on the RFP that advanced a bank bid to final negotiation
Role: Solution Architect (Bid Support)
Executive summary
Drove the architecture and technical-writing portions of major RFP/RFI responses for Financial Services — the flagship being a bank's Cloudera-to-Azure data-platform bid that advanced to final negotiation.
- Azure Databricks
- Microsoft Fabric
- Microsoft Purview
- Azure Pricing Calculator
- Visio / PowerPoint
A mid-size bank's data-platform RFP put a long-running Cloudera estate up for renewal, forcing a choice between re-licensing on-premises infrastructure and migrating to a cloud data platform under competitive pressure. I joined the pursuit team to own the solution architecture, cost estimates and the technical sections of the response—a bid stage every major account pursuit runs, with fixed dates and heavy internal coordination.
- Solution architecture: read requirements and design a solution diagram mapping all components to Azure services, differentiating our solution.
- Estimations & calculators: build/validate pricing estimates (Databricks units, Fabric capacities) and competitor cost comparisons.
- Proposal writing: draft technical approach, requirement-by-requirement responses, SLA compliance and project plan in clear, professional language.
- Internal review & iteration: collaborate with account execs, PMs and partners to incorporate feedback.
- Run the response through an internal red-team review and tighten messaging before submission.
I started with a pursuit-team workshop to fix the bid's scope, then designed an Azure architecture migrating Cloudera to Azure Databricks + Fabric covering pipeline and zone diagrams, security and performance compliance, and a phased migration timeline. I built an Azure Pricing Calculator cost breakdown highlighting TCO against the Cloudera baseline—the single most-discussed artifact with the account team, which is why every line was re-checked against the calculator before submission. After an internal red-team review tightened the messaging, the response was submitted on the fixed date. The same working pattern (workshop → architecture → costing → writing → red team) was reused on subsequent RFP/RFI pursuits for other Financial Services accounts.
The flagship bank response scored top technical marks and advanced to final negotiation, with the clear architecture and cost breakdown credited as what carried it there. Across other pursuits supported the same way, several responses scored top technical marks and reached shortlisting for orals. The RFP materials became reusable assets that accelerate later proposals.
The RFP process taught structured communication under constraints—the red-team round is now a step I run earlier rather than at the end, because skepticism improves a bid most while it can still be rewritten. It also focused my writing on what the client cares about rather than showcasing tech. Coordinating many contributors improved my project management under pressure, and accuracy in costing is crucial—minor oversights erode trust.