How We Built the AI-Powered Tender Application Workspace

Winning a government tender in South Africa requires more than just finding the right opportunity. You need to prepare a compliant response package: cover letter, capability statement, methodology, pricing schedule, SHEQ plan, quality plan, and technical proposal — each tailored to the specific tender's requirements. For a small supplier, this preparation work can take 40-80 hours per bid.

The Application Assistance Workspace was built to reduce that burden. It's a comprehensive workspace where subscribers can track applications on a Kanban board, generate tender-specific response documents using AI, plan their submission timeline, research the buyer and competition, and manage compliance checks — all from a single interface.

The Blueprint System

Every tender application starts with a blueprint — a deterministic derivation of what the tender needs and what the user must prepare. The blueprint engine runs in two layers:

Copy
1export type ResponseDocKind =
2    | 'cover_letter' | 'capability' | 'methodology' | 'technical'
3    | 'quality' | 'sheq' | 'pricing' | 'declaration'
4    | 'undertaking' | 'acknowledgement' | 'email' | 'other';
5
6export function deriveBlueprint(input: DeriveBlueprintInput): ResponseBlueprint {
7    // Layer A: Pure deterministic derivation from tender analysis
8    // - requiredUserDocuments: Tax Clearance, BBBEE cert, CSD, CIDB
9    // - responseDocuments: Cover letter, Capability, Methodology + tender-specific
10    // - steps: Briefings, clarifications, document gathering, compliance, submission
11    // - submission: Method (portal/email/physical), deadline, contact
12    // - risks: Long-lead docs, passed briefings, tight deadlines
13    // - confidence: Based on AI confidence score or analysis substance
14}
15
16// ... (truncated)
Show More (6 more lines)
TYPESCRIPT

Layer A is deterministic and runs instantly. It derives the required documents from the tender's structured data: what category is it, what mandatory documents are listed, what evaluation criteria apply. Layer B is the AI enrichment that merges tender-specific extras: if the AI analysis detects that this tender requires a specific environmental impact assessment that isn't in the standard checklist, it adds it. The layers are de-duplicated to avoid conflicting recommendations.

Document Generation Pipeline

The document generation pipeline is where AI meets production. When a user clicks "Generate Cover Letter," the system:

Copy
1export async function generateResponseDocument(
2    input: GenerateResponseDocInput,
3): Promise<GeneratedResponseDoc> {
4    // 1. Build resolvable map from company identity data
5    const resolvable = buildResolvableMap(toGroundingInput(input));
6
7    // 2. Generate via Gemini AI with grounded prompt
8    const content = await geminiClient.generateContent(
9        buildPrompt(input),   // Authoritative data + tender context + company profile
10        systemInstruction,    // "You are an expert in SA government tender applications..."
11        { temperature: 0.6, maxTokens: 4000 }
12    );
13
14    // 3. Audit for unresolved placeholders
15    const audited = auditPlaceholders(content, resolvable);
16// ... (truncated)
Show More (8 more lines)
TYPESCRIPT

The key insight is that AI-generated documents are grounded in real data. The Gemini prompt includes the tender description, eligibility criteria, evaluation method, the company's profile (services, B-BBEE level, CIDB grade, provinces), and the specific document type being generated. The system prompt instructs Gemini to follow South African tender conventions — proper SBD form references, PPPFA compliance language, and professional formatting.

After generation, the system audits the output for unresolved placeholders. If the AI hallucinated a company name or left a [Insert Name] marker, the audit catches it. If the AI generation fails entirely, the system falls back to a typed template that the user can fill in manually.

The Kanban Board and Application Lifecycle

The workspace is organized as a Kanban board with columns representing the application lifecycle: Draft (new applications that need attention), Preparation (active document generation and research), Submitted (recorded as submitted with method and reference), Under Review (tracking post-submission), Accepted or Not Successful (final outcomes).

Card transitions are persistent and sync across devices. Manual moves hold until the actual work progress overrides them — so if the closing date passes, the card automatically moves to the appropriate status. Past-due draft applications are swept off the board automatically, with a notice showing how many were removed.

Timeline Planner and Reminders

The workspace automatically schedules key milestones: the compulsory briefing session date (extracted from the tender documents), clarification deadline, document gathering period (with enough buffer for long-lead items like tax clearance certificates), submission deadline (with progressive reminders at 7 days, 3 days, and 24 hours), and post-submission follow-up reminders for award notifications. Reminders are delivered via in-app notifications and email.

Market Research Panel

Each workspace includes a market research panel that shows: the issuing organisation's profile (past tenders, award patterns, typical evaluation timelines), likely competitors (who has won similar tenders from this buyer historically), eligibility snapshot (B-BBEE requirements, CIDB grade requirements, mandatory documentation, all checked against the user's company profile), and relevant procurement intelligence (recent policy changes, audit findings affecting this buyer).

The Deep Analysis Pipeline

When a user clicks "Deep Analysis," the workspace triggers a comprehensive analysis of the tender documents. The system reads the densest document extracts (not just the first three rows), classifies content into 15+ section types (scope of work, eligibility, evaluation criteria, submission requirements, contractual terms, etc.), extracts disqualifiers and watch-outs that could trip up the bid, and generates a tailored requirements list, document checklist, and step-by-step preparation plan. The deep analysis runs asynchronously — the user is told to come back once it completes.

Document Intelligence

The Document Intelligence module classifies every document the tender requires into three categories: included in tender documents (already provided — user just needs to download and complete), in the user's profile (already uploaded — user can reuse directly), and must obtain (external documents like tax clearance, B-BBEE certificate — these need proactive action). For each must-obtain document, the system provides acquisition guidance: where to get it, how long it takes, and what to watch out for.

From Chatbot to Workspace

The workspace replaced an earlier AI chatbot approach in July 2026. The chatbot was conversational but unstructured — users asked questions, the AI answered, but nothing was saved or actionable. The workspace inverted the model: instead of a chat-first interface, it's a structured workspace where AI assists within defined workflows. The global AI assistant is still available for general questions, but the workspace is where the real work happens.