November 4, 2025

Company

Shipping AI That Works: Built x MightyBot Draw Agent

"Once you see Draw Agent in action, you can’t unsee it. This is undeniably the future as it’s truly better, faster, and cheaper than the alternative." — Chase Gilbert, CEO of Built

By Stefan Fox (MightyBot) with Thomas Schlegel (Built Technologies)

TL;DR

  • Three Built customers live in production with a phased rollout: Audit → Assist → Full Auto
  • 95% time reduction on draw reviews—completed in as few as 3 minutes
  • 99%+ accuracy in production; agents found issues human teams consistently missed
  • "Next‑day fixes" became the working norm through daily sprints and SME feedback loops
  • The Draw Agent runs on the MightyBot platform (tools, indexing, workflows, evals)
  • Approach: meet the enterprise where it is—an AI exoskeleton over existing systems

The Collaboration

Thomas leads a “new bets” team at Built, which manages a significant portion of U.S. construction lending. The problem was well understood: loan admins review draw packages with hundreds of documents, reconcile data, check compliance, and make funding decisions. It's slow, repetitive, and high‑stakes.

From day one, our shared goal wasn't a demo; it was production. Built had the data, the workflows, and real customer demand. MightyBot brought a platform for repeatable, reliable Agentic AI workflows and an operating cadence designed for speed.

Thomas's perspective: Speed meets existing platform

The search for the right partner was extensive—I evaluated close to 20 different AI solutions. What I was looking for was specific: a small, scrappy team with forward-deployed engineering capabilities, shared incentives, and the ability to be nimble. Once I saw the AI technology landscape clearly, I realized there was a new existential threat. We could either lead this transformation or watch someone else disrupt our industry.

What struck me most about MightyBot's approach was how their platform met us exactly where our technology was. We didn't need to re-architect our entire system. Instead, we created what I call an AI exoskeleton for our existing platform—wrapping our existing infrastructure with intelligent automation. The result? We went from concept to production with customers in about three months, which would have been impossible starting from scratch.

We operated on daily sprints rather than traditional two-week cycles. Within the first week, we had a working version of the product. This wasn't just about moving fast—it was about a fundamentally different way of building software that brought joy back to the development process.

The Perfect Fit: Policy‑Driven Automation

MightyBot's platform is built on policy‑driven automation—a design philosophy where AI agents execute clearly defined business rules rather than making autonomous decisions. Construction lending turned out to be an ideal application for this approach.

In real estate finance, every lender has their own policies: specific insurance requirements, permit validations, inspection protocols, and disbursement rules. Traditional approaches would either force everyone into the same rigid box or create an unmaintainable forest of if-then rules.

With MightyBot's approach, lenders define their policies in natural language, and the AI consistently enforces those policies across every draw. The agent understands and applies each lender's specific business rules—no rigid templates, no unmaintainable code branches.

This approach proved ideal for construction lending:

  • Scalability: New lenders onboard by defining their policies, not by forking code
  • Consistency: Every draw gets the same thorough review according to defined policies
  • Auditability: Every decision traces back to a specific policy requirement
  • Trust: Lenders see their own business rules reflected perfectly in the agent's behavior

The MightyBot platform philosophy—that AI agents should be transparent executors of well-defined business policies rather than black boxes making autonomous decisions—turned out to be exactly what the lending industry needed.

UX and Design Principles: Agents and people

We designed the agent for the people doing the work every day—grounded in interviews, workflow reviews, and hands‑on testing with loan admins. The result is a system of action that feels familiar, trustworthy, and helpful from the first use.

  1. Human‑centered design research: co‑created with SMEs through ride‑alongs, reviews, and rapid feedback loops
  2. Familiar mental models: table views, side‑by‑side comparisons, and clear status states
  3. Transparency by default: every decision shows its evidence and rationale
  4. Progressive control: Audit → Assist → Auto to build confidence at each step
  5. Action over alerts: findings grouped by the single action that resolves them. This makes messages to borrowers and builders more intuitive.
  6. Explainable and auditable: plain language, consistent patterns, traceable outcomes. Users can see and understand everything the agent does, both while it's happening and then after the fact via the compliance reporting.
  7. Assist‑first onboarding: a copilot that speeds work; never a black box that replaces it
  8. Feedback in the flow: lightweight approvals and reactions that drive continuous improvement

Outcome: Users felt enabled—not threatened. Early demos consistently landed as "this makes my job easier," accelerating adoption and paving the way to Assist and Full Auto.

How We Built It: The AI Exoskeleton Pattern

One of the things that can be intimidating when you're going to build your first agentic product is that every company has some amount of technical debt. We created an AI exoskeleton around Built's existing platform. This insight shaped everything. Instead of forcing a rebuild, we wrapped our existing systems:

Integration principles

  • Core business logic stays in the existing backend
  • Agent consumes fat endpoints and writes back through existing APIs
  • Humans retain control: Assist mode for review, Full Auto where appropriate
  • Customization stays safe: Steerability handles per-lender nuances without code changes

Platform primitives that scale

  • Multi-LLM routing and fallback strategies
  • Document extraction and structured outputs
  • Search/indexing layers for text and embeddings
  • Workflow orchestration with evaluation harnesses

Properties of a Successful AI Project

  1. Policy‑driven execution: Codify business rules once; enforce them consistently at scale.
  2. Predictable automation where it matters: Deterministic flows for critical work; intelligent assistance for the rest.
  3. Seamless fit with existing systems: Integrates without re‑architecture; meets you where you are.
  4. Human‑centered oversight: Present actions, not noise; make approvals effortless.
  5. Transparent and auditable: Every decision is explainable and traceable.
  6. Rapid improvement loop: SME feedback turns into next‑day enhancements.
  7. Proof over promises: Validate on historical and live data before broad rollout.
  8. Compounding data advantage: Operations generate insights that improve outcomes over time.
  9. Enterprise‑grade resilience: Built for spikes, reliability, and scale.
  10. Security and governance by design: Controls aligned to regulated environments.
  11. Platform foundation: Reusable capabilities that travel across use cases and teams.

Working Cadence: Daily Sprints, Next‑Day Fixes

Our loop was simple and relentless:

  • SMEs (loan admins) recorded quick Looms with real draws
  • Engineering reviewed the same day and shipped fixes overnight
  • We repeated this daily

This cadence turned into an expectation: if something wasn't right, it was fixed the next day. That rhythm—paired with production data—drove accuracy and trust.

What made this possible was MightyBot's AI‑first approach to everything. From meetings to requirements documentation to design feedback sessions, every aspect of the process leveraged AI. This wasn't just about using AI tools—it was a fundamentally different way of working that made software development enjoyable again.

Thomas's view: Widening the circle of AI contributors

What really validated this approach was seeing operations teams invite risk teams to calls—not to solve problems, but to marvel at issues the agent discovered that had never been uncovered before. These were incredibly nuanced checks buried deep in PDFs: a builder's risk policy missing the mortgagee clause on page five in tiny print, building permits with almost-but-not-quite matching addresses, duplicate line items across multiple invoices.

The reality is that humans simply don't have time to perform 100% of these checks on every draw. They're reading through hundreds of pages, and it's impossible to catch everything. The agent doesn't get tired, doesn't miss the fine print, and checks everything, every time.

Building Trust: The Path to Full Auto

While we moved fast on development, customer adoption followed a deliberate progression:

Audit ModeAssist ModeFull Auto

This phased approach allowed lenders to:

  • Start with transparency: see every decision the agent makes
  • Build confidence through accuracy: watch the agent catch issues humans miss
  • Graduate to efficiency: move to assist mode once trust is established
  • Achieve autonomy: enable full auto for qualifying draws

Thomas's experience: Converting the skeptics

One of my favorite moments came with a customer who was known for having a tried and true way of doing things. This was someone with decades of experience, having managed this process manually with great success. I went in expecting a healthy dose of skepticism.

After a 15 minute demo, their reaction completely surprised me: “I’ve been driving the Honda Civic. Please give me the keys to the Ferrari.” That’s when I knew we had built something truly transformative, when a seasoned expert who has perfected their manual process becomes your biggest champion in minutes.

What We Shipped (Confirmed Outcomes)

July–October 2025 results across design partners:

  • Production: three customers live; one on Full Auto for qualifying draws
  • Speed: 2–5 minutes per agent review (avg: 3 minutes)
  • Quality: agents surfaced issues human teams missed in already-approved draws
  • Accuracy: Started targeting 80%, achieved 99%+ in production
  • Scale: hundreds of thousands of documents processed in test and production flows
  • Operability: clean assist‑mode UX with consolidated, resolvable actions

Beyond these metrics, we created an entirely new data asset. The policy-driven automation generates rich data on policy adherence, human feedback patterns, and opportunities for process improvement. This data becomes more valuable over time, enabling continuous refinement of both policies and agent performance.

Thomas on MightyBot: Exceeding our wildest expectations

When we started, our initial target was 80% accuracy—that's what we thought human-level performance looked like based on our data. We figured if we could hit 80%, we'd be saving significant time even with some errors to correct.

The reality blew us away: we're at 99%+ on everything, all the time! Not only is the agent more accurate than human reviewers, it's doing a more exhaustive review in a fraction of the time. It's checking things that humans simply don't have bandwidth to verify on every single draw.

What I appreciated most about MightyBot was finding a partner who could go deep and fast while keeping our options open. The platform approach gave us both—immediate value on draw processing while maintaining flexibility for future use cases. This isn't a one-trick pony; it's infrastructure we can build on for years to come.

Why This Worked

The Draw Agent is a workflow running on the MightyBot platform. That matters because the next use cases don't require re‑inventing the stack. The same primitives—tools registry, data/indexing, workflow orchestration, evaluation, steerability—power future use cases.

  • A clear, valuable job‑to‑be‑done (draw review) with well‑defined SOPs
  • Real production data from day one of testing
  • MightyBot is a platform that meets enterprises where they are—no re-architecture or migration work is required
  • A shared operating model (daily sprints, next‑day fixes) that built trust quickly
  • A phased rollout that balanced speed with earning customer confidence
  • MightyBot's policy‑driven automation proved to be the perfect fit for regulated lending workflows

If you're evaluating your first agentic product and wrestling with current infrastructure, our biggest lesson is simple: you don't need to re‑architect to get value. Start where you are. Wrap the core workflows with an AI exoskeleton. Ship, learn, and iterate—but always with your customers' trust at the center.

— Stefan & Thomas

Related Posts

See all Blogs