Apr 6, 2026
How We Built an AI System That Automates Senior Solution Architect Workflows
Discover how we built a 4-agent AI co-pilot that converts complex RFPs into draft technical proposals in 15 minutes — with built-in conflict detection, assumption surfacing, and confidence scoring.
Author


Book a call
Table of Contents
30% of a senior architect's time goes into reading RFPs and writing proposals rather than designing systems or solving engineering problems.
A 50-page enterprise RFP lands in an inbox. Two hours later, the architect has concluded what they suspected on page three: React Native frontend, Node backend, PostgreSQL, and Stripe for payments. The decision was predictable, but the process was manual and time-consuming.
What the AI Presales Co-Pilot Does
This system assists with the presales cycle. You upload a client's documents—PDFs, Word docs, Excel sheets, or emails—and the system produces a draft technical proposal that an architect can review and refine in 15 minutes instead of writing from scratch for 3 hours.
The value extends beyond document generation to reasoning:
- Detects Contradictions: It flags tensions, such as a request for Native Mobile only paired with Critical SEO.
- Surfaces Assumptions: It states the assumptions it is making (e.g., assuming Stripe for payments) so an architect can confirm or override them.
- Confidence Scoring: It scores its own decisions, indicating where reviewers should focus attention.

How It Works: Four Specialized Agents
The system runs four specialized AI agents in sequence. The entire pipeline runs over a WebSocket connection, streaming progress to the dashboard in real time.

Agent 1: Requirement Interpreter
This agent parses raw, unstructured documents using format-specific tools (PyMuPDF, pandas, etc.). It extracts features, technical constraints, and non-functional requirements.
- Pattern Enrichment: If a two-sided marketplace is mentioned, the system suggests features like ratings and booking based on a built-in knowledge base.
- Conflict Detection: A rule engine identifies over-engineering or technical mismatches during initial analysis.
Agent 2: Solution Engine
This agent produces tech stack recommendations and effort estimates. It uses a hybrid approach: deterministic rules suggest the baseline stack (e.g., NestJS/PostgreSQL), while the LLM validates that choice against the specific client context. Effort estimation provides optimistic-to-pessimistic ranges (e.g., "120–210 hours") to reflect real-world uncertainty.
Agent 3: Self-Critique
Before a proposal is written, a critique agent reviews the solution for consistency. If an assumption contradicts a user input, the system sends a clarifying question back to the architect via WebSockets. Only when the critique approves does the pipeline proceed to generation.
Agent 4: Proposal Composer


The Pipeline at a Glance
| Stage | Role | Output |
|---|---|---|
| 1. Parse | Ingestion of any file type | Combined raw text |
| 2. Extract | Conflict & pattern detection | Structured requirements JSON |
| 3. Design | Rule-based stack matching | Solution + effort mapping |
| 4. Review | Validation & User Clarification | Approved technical solution |
| 5. Write | Template-based generation | Polished Markdown/PDF proposal |
Engineering Insights
Rule-based systems and LLMs complement each other: Conflict detection and effort mapping do not need an LLM—they need deterministic rules. LLMs handle ambiguity and prose generation.
The Technical Stack
- Backend: Python with FastAPI for async orchestration.
- AI Layer: OpenRouter (Claude, GPT-4, and Gemini) for multi-model reasoning.
- Communication: WebSockets for real-time streaming to a React-based frontend.
- Knowledge Base: JSON-based datasets for requirement patterns and stack decision rules.

Subscribe to Our Newsletter
Subscribe to RSS
Press & Media Hub RSS FeedRelated Articles.
More from the engineering frontline.
Dive deep into our research and insights on design, development, and the impact of various trends to businesses.

Jun 25, 2026
Analytics Insight Features GeekyAnts' Blueprint for Future-Ready Manufacturing
Analytics Insight features GeekyAnts CEO Kumar Pratik's take on why isolated automation efforts fall short, and what it takes to build truly future-proof manufacturing systems.

Jun 25, 2026
Automating Loan Origination Workflows: From SAR Prep to Fraud Checks
A guide to automating SAR preparation and fraud checks within the loan origination workflow, covering U.S. regulatory requirements and how lenders can adopt automation without disrupting operations.

Jun 19, 2026
We Built a 114-Second AWS-to-Azure Failover. Here’s What We Learned
A practical guide to building a 114-second multi-cloud disaster recovery failover between AWS and Azure — what we built, what broke, and what we learned.

Jun 17, 2026
Google I/O 2026 Mobile Playbook: AI Studio, Android CLI, and Antigravity for App Development
Google I/O 2026 shifted mobile development from code assistance to full lifecycle delivery. This blog breaks down what that means for Android, Flutter, and React Native teams.

Jun 17, 2026
Beyond the Chatbot: Architecting Enterprise Workflows with Managed Agents in the Gemini API
A practical guide to building production-ready agentic workflows with Google's Managed Agents API, covering architecture, governance, and where enterprise teams should start.

Jun 16, 2026
Integrating AI with Wearable Healthcare Apps: Architecture, Compliance & ROI
A technical and compliance-focused guide for U.S. healthcare founders and providers on building AI-enabled wearable healthcare apps across architecture, compliance, and ROI.