Skip to content

Integration & deployment

It has to land where the work already happens

A model that only runs on our machines is not much use to an estimator with a bid due on Friday. How the output gets delivered matters as much as how good it is.
  • API, batch or on-prem
  • Your schema and field names
  • You own the trained weights
Diagram of a floor plan processing pipeline from drawing ingestion through detection stages to structured output
The same pipeline, delivered three different ways.

Three shapes

Pick the one that matches who uses it

Most projects end up as one of these. The pipeline underneath is the same; what changes is where it sits and who touches it.
  • An API inside your product

    Your platform posts a sheet and receives JSON in your own field names. Nothing in the response names us.
    For software teams
    For software products
  • A batch job for your team

    A folder of drawings in, populated takeoff sheets out. No integration work, no new tool for estimators to learn.
    For estimating and QS teams
    For estimating & QS
  • A service in your network

    Deployed in your own cloud account or on your servers, so confidential drawings never leave your boundary.
    For regulated and sensitive work

Drawings and confidentiality

Your plans stay yours

Construction drawings carry commercial sensitivity and often contractual restrictions. That shapes deployment more than any technical consideration.
  • NDA signed before any drawings are shared
  • Deployment in your own cloud account or on-prem where required
  • Your drawings are never used to train models for other clients
  • You own the weights trained on your data

Read how this works alongside fine-tuning, where the same restrictions apply to the training data.

Human in the loop

Built to be checked, not trusted blind

Every output carries confidence, and anything below your threshold routes to a person rather than into your database.
  • Review queue

    Low-confidence values are held for a person, with the overlay showing exactly what the model saw.
  • Corrections feed back

    What a reviewer fixes becomes training data for the next round, so the queue shrinks over time.
  • Thresholds are yours

    Where the bar sits is a business decision — publishing a listing and pricing a bid are not the same risk.

Start here

Start with the output, not the plumbing

Integration is the easy half once the extraction is right. Send one sheet, see what comes back, and the delivery question answers itself.
  • One sheet is enough — PDF, DXF or a scan
  • Back in about 2 business days, with an annotated overlay
  • No call required, NDA on request

Send us one sheet

We run it through our floor plan models and send back the extracted data with an annotated overlay, so you can see what comes off your own drawings before anyone books a call.

  • Back in about 2 business days
  • PDF, DXF or a scan
  • NDA on request
This is our base model, before any tuning for you. On a paid project we train it further on your own drawings, which is where the rest of the accuracy comes from. So this shows you the starting point, not the best we can do.

By submitting, you agree to our Privacy Policy. We never share your details.

FAQ

Questions, answered

Practical questions about running it.

Not there yet? Start with one sheet.

  • No. There is no sign-up page, no API key to generate and no price list, because every deployment runs a model tuned to one client's drawings. What we deliver is an endpoint built for you, with the fields you agreed.

Get in touch

Tell us what is on your drawings

Describe the sheets you get and what you need off them. We will tell you what our models already handle, what needs fine-tuning on your drawings, and what is not worth automating at all.

Reply time
Within 1 business day

Would rather show than tell? Send one sheet for a free analysis

We reply within 1 business day.

By submitting, you agree to our Privacy Policy. We never share your details.