Skip to main content
Web Design & Development · Case studies

What web design looks like in the real world.

Websites engineered as lead-generation systems, not online brochures. Below are example projects where this service moved the business outcome — not just the design.

In one paragraph: what does web design look like at Ampex?

Websites engineered as lead-generation systems, not online brochures. The engagements below are illustrative web design projects shipped by our senior in-house team on a fixed scope and fixed price in Indian Rupees, with reported outcomes drawn from the client's own analytics, ad platforms or CRM. Named client details are shared under NDA once we're at proposal stage.

  • B2B enquiry to order flowA buyer RFQ arrives via WhatsApp or web, is tracked in the CRM pipeline, quoted and followed up, and converts to an order. Stages: Buyer RFQ → WhatsApp / Web → CRM pipeline → Quote & follow-up → Order.Buyer RFQWhatsApp / WebCRM pipelineQuote & follow-upOrderB2B ENQUIRY TO ORDER FLOW
    Example · 02Precision-parts manufacturer · Coimbatore

    Complete digital business setup for a B2B manufacturer

    A 20-year-old precision-parts manufacturer still ran on phone calls, paper ledgers, and informal WhatsApp quotes — with no online presence, CRM, or centralised quotation history.

    Results & Impact
    Inbound enquiries now tracked end-to-end
    Inbound enquiries now tracked end-to-end: 100%
    Faster quote turnaround
    Faster quote turnaround:
    Qualified pipeline in first quarter
    Qualified pipeline in first quarter: ₹14L+
    From kickoff to live online presence
    From kickoff to live online presence: 5 weeks
    Technologies used
    • React
    • Supabase
    • n8n
    • Razorpay
    • Google Workspace
    • Meta Pixel
    5 weeks · Setup sprint · fixed priceAsk about this project
    Client industry
    B2B precision-parts manufacturing
    Timeline
    5 weeks · Setup sprint · fixed price
    Technology stack
    React, Supabase, n8n, Razorpay, Google Workspace, Meta Pixel
    Problem

    The company had built its reputation through direct relationships, but new buyers could not find them online. Every RFQ had to be rebuilt from memory or old WhatsApp messages. The sales team had no shared pipeline, no follow-up reminders, and no visibility into why deals were lost. Quarterly reviews were guesses because there was no record of what had been quoted or promised.

    Objectives
    1. Make the company discoverable on Google and LinkedIn for its part categories.
    2. Standardise RFQ intake so every enquiry lands in one shared pipeline.
    3. Cut quote turnaround from 2–3 days to under 24 hours.
    4. Give leadership a single dashboard for pipeline, wins, and lost-reason data.
    Implementation
    1. Week 1 · Discovery

      Audited existing catalogues, WhatsApp threads, and paper ledgers; interviewed the sales team about how deals actually get closed.

    2. Week 2 · Foundation

      Registered the branded domain, set up Google Workspace, and rebuilt the product catalogue with clean naming and specs.

    3. Weeks 3–4 · Website + RFQ engine

      Shipped the corporate website with per-category RFQ forms and a WhatsApp-first enquiry flow that also writes to the CRM.

    4. Week 5 · CRM + go-live

      Configured the pipeline, follow-up nudges, and reporting; trained the sales team; cut over the old WhatsApp-only enquiry number.

    Challenges encountered
    • Product data existed only in a mix of PDFs and printed catalogues — a full re-typing and spec-cleanup pass was needed.
    • The senior sales team was WhatsApp-native and resisted a CRM until the pipeline mirrored their existing mental model.
    • Historical enquiry data was unrecoverable; the team started with a clean slate rather than a migration.
    Solutions
    • B2B website + RFQ engine. A corporate site with a product catalogue, instant RFQ forms, and a WhatsApp-first enquiry flow so buyers could discover and reach the company in seconds.
    • Lightweight CRM with follow-up discipline. Every enquiry is logged, RFQ-to-order status is tracked, and the system nudges sales reps before deals go cold.
    • Business-ready foundation. Branded domain, Google Business Profile, Google Workspace, analytics, and a clean e-invoice-ready data structure for future accounting integration.
    Client testimonial

    Not published. This engagement is under NDA. We can arrange a reference call with the client at proposal stage — we do not publish paraphrased or synthesized quotes.

    Lessons learned
    • For legacy manufacturers, adoption depends on the CRM matching WhatsApp habits, not the other way round.
    • A clean product catalogue is worth more than a fancy website — it is the asset the sales team uses every day.
    • 'No historical data' is often a feature: the new pipeline starts trustworthy on day one.

    Illustrative workflow example. Named client case studies are shared on request where permitted.

  • Citation-verified research pipelineA judgment PDF is parsed and structured, indexed with hybrid search, verified for citations, and returned as an answer. Stages: Judgment PDF → Parse & structure → Hybrid search → Citation verify → Answer.Judgment PDFParse & structureHybrid searchCitation verifyAnswerCITATION-VERIFIED RESEARCH PIPELINE
    Example · 03Legal-tech SaaS · Delhi NCR

    Citation-verified AI research engine for a legal-tech startup

    A legal-tech startup needed a defensible AI layer over Indian case law without the hallucinated citations that were destroying trust with senior counsel.

    Results & Impact
    Citation accuracy in blind evaluation
    Citation accuracy in blind evaluation: 94%
    Judgments processed automatically
    Judgments processed automatically: 1,200/day
    Reduction in lawyer research time
    Reduction in lawyer research time: 70%
    Enterprise pilots signed post-launch
    Enterprise pilots signed post-launch: 3
    Technologies used
    • Python
    • React
    • PostgreSQL + pgvector
    • GROBID
    • Claude
    16 weeks · MVP to pilot · fixed scopeAsk about this project
    Client industry
    Legal-tech SaaS
    Timeline
    16 weeks · MVP to pilot · fixed scope
    Technology stack
    Python, React, PostgreSQL + pgvector, GROBID, Claude, Supabase
    Problem

    Junior lawyers were spending 8–12 hours per matter manually reading judgments to extract parties, statutes, and precedents. Existing general-purpose LLMs confidently returned wrong citations, which made enterprise clients nervous and stalled paid pilots. The founders needed a system that could cite every answer back to a real paragraph in the source document.

    Objectives
    1. Automate structured extraction of parties, statutes, and holdings from Indian judgments.
    2. Guarantee every AI answer resolves to a real paragraph in the source PDF.
    3. Reach 90%+ citation accuracy in blind evaluation before pilot handover.
    4. Ship a reviewer console so in-house lawyers can correct extractions in-flow.
    Implementation
    1. Weeks 1–2 · Discovery + evaluation set

      Sat with senior counsel to define what a correct citation looks like; built a 500-judgment blind evaluation set before writing pipeline code.

    2. Weeks 3–6 · Ingestion pipeline

      Parsed judgment PDFs with GROBID, structured into parties, statutes, holdings, and paragraphs; loaded into Postgres with pgvector.

    3. Weeks 7–10 · Retrieval + answer engine

      Hybrid BM25 + vector retrieval, followed by a citation-verification step that rejects any claim not anchored to a real paragraph.

    4. Weeks 11–13 · Reviewer console

      Built the lawyer-in-the-loop UI: accept, reject, or correct extractions; corrections feed back into evaluation.

    5. Weeks 14–16 · Pilot hardening

      Ran the blind evaluation with two enterprise buyers, tuned thresholds, and shipped the pilot handover doc.

    Challenges encountered
    • OCR quality on older scanned judgments was poor; a pre-clean step and a per-court PDF quality profile were required.
    • Statute references use inconsistent shorthand across courts, so a normalisation layer had to be maintained by hand initially.
    • Enterprise legal teams wanted a full audit log of every AI decision — added append-only citation logging late in the build.
    Solutions
    • Judgment ingestion pipeline. PDFs are parsed, structured into parties, statutes, holdings, and paragraphs, and indexed with hybrid BM25 + vector search for fast retrieval.
    • Citation-verified answer engine. Every AI-generated claim must anchor to a source paragraph before it is shown to the user — no hallucinated precedents.
    • Lawyer-in-the-loop feedback loop. A reviewer console lets in-house lawyers accept, reject, or correct extractions, with corrections feeding back into model improvement.
    Client testimonial

    Not published. This engagement is under NDA. We can arrange a reference call with the client at proposal stage — we do not publish paraphrased or synthesized quotes.

    Lessons learned
    • In regulated verticals, an auditable citation chain sells more than any raw accuracy number.
    • The evaluation set is the product — write it first, revisit it every fortnight.
    • Lawyer-in-the-loop is not a fallback; it is the reason the system is trustworthy enough to sell.

    Illustrative workflow example. Named client case studies are shared on request where permitted.

Ready to ship web design?

Tell us where you're stuck. Get a fixed-scope plan in 48 hours.

Faster leads via WhatsAppFixed pricing in ₹ with GST invoiceReply within 1 working day IST