Getting started

Finish your first construction task.

Start with a scope, a plan PDF, or the sample job. Keep quantities, supplied rates, and assumptions together.

A scope to a proposal

  1. Supply the scope. Paste it into mud1 or upload a document. Check the extracted project facts and flag missing information.
  2. Verify quantities. Printed dimensions and text do not establish a calibrated plan measurement. Use Takeoff for lengths, areas and counts.
  3. Add your rates. Use Quick Bid for a worksheet. Check regional defaults against your own labor, equipment, material and subcontractor costs.
  4. Prepare the proposal. Ask mud1 to draft it with your supplied prices, or use the proposal editor. Review exclusions, markup and the total before exporting.
  5. Build a preliminary schedule. Enter scope, phases and dates in the schedule builder. Verify dependencies, crew availability and working days before use.
Measure a PDF and use the quantities

Open Takeoff, choose a PDF, and select Analyze plan set. Up to 50 pages and 40MB are supported.

  1. Select the page, unit and known distance.
  2. Click the two points of a verified dimension to calibrate. Recalibrate after changing units or sheet scale.
  3. Use Distance, Polyline, Area or Count. Check the layer and measurement list.
  4. Export CSV or JSON, or select Use in chat. The composer shows which saved takeoff is included.

Text search uses the PDF text layer. Scanned plans can be measured manually. OCR, automatic symbol matching and pipe tracing are not available on the website yet.

Create and export a proposal

The proposal editor works without hosted AI. Enter the company, client, scope, prices and exclusions. Review the preview, then export PDF, text or HTML.

In chat, ask for a named file and open the returned document. Check its contents before sharing. The sample job uses supplied prices and should total $41,140 after 10% markup.

Browser, Mac app and local mud1

The browser supports project documents, manual takeoff, calculators, worksheets and hosted chat. Saved browser data stays tied to that browser and device; export important work or use Save backup.

The Mac app adds local folder access and project mirroring. Local mud1 requires Ollama and the model on your computer. Test local mud1 is separate from hosted mud1.

If hosted AI is unavailable

Your conversation stays saved. A temporary request failure may be retried; an account/service outage requires the openmud operator to restore service.

Keep working with calculators, Quick Bid, the proposal editor, or manual takeoff.

Building openmud? See the developer architecture and source access.