A-1 Zemin

From Bid to Build

One cost code from the won bid to the last foot of pipe in the ground. Operating software for self-perform water, sewer, storm and gas contractors.

Catch the shortage before the crew is short in the trench.

JOB-2631 HarborviewPrototype

"Laid 120 feet of 8-inch C900 from 3+40 to 4+60. Hit an unmarked gas service at 4+10 and stood down two hours. Need four more 8-inch megalugs tomorrow."

Production410 · 120 LF · 3+40 to 4+60
Delay900 · 2 HR · unmarked gas
Material8" MJ megalug · 4 EA
Short 48 megalugs needed for 4 MJ fittings. 4 ordered.
Invented placeholder job and note. Field notes are in development.
C-1 The spine

Everything hangs off the cost code.

Conform the budget once. Every schedule task, takeoff item, field hour and change estimate posts to that same code, so the field and the office work from one set of numbers.

No re-keying the estimate into job costing. No second spreadsheet to find out what the crew actually put in the ground.

The cost-code spine Cost code 410, 8 inch C900 water main install, in the center. Four leaders connect it to a schedule task, a takeoff item, field hours and a change estimate. WON BID: 410 BUDGETED 1,240 LF 410 8" C900 water main install SCHEDULE TASK TAKEOFF FIELD HOURS CHANGE ESTIMATE Install 3+00 to 6+00 12 days, FS after potholing 1,240 LF pipe 8 megalugs, 4 MJ bends 120 LF, 3+40 to 4+60 Crew 2, from the foreman note 2 HR standby Unmarked gas at 4+10
C-2 Bid to build

Every stage of the job, on the same cost codes.

Here is what works today and what comes next. Keep your estimating software for now. When Zemin's estimating arrives, it learns from your own finished jobs, not a generic cost database.

B

The bid

Estimates feed the budget directly, so nothing gets re-keyed. Estimating itself is sequenced last.

Later
S-1

Budget conform

Turn the won bid into cost codes once, instead of re-keying the estimate into a separate job costing system.

Built
S-2

Cost-coded schedule

Tasks carry budgeted hours on the same codes, with predecessors, lags and baseline against actual dates.

Built
S-3

Takeoff with checks

Quantities sit on the code, and restraint checks flag a megalug shortage before the order goes out.

Built
R

Field notes to coded work

The foreman talks for twenty seconds. Zemin proposes coded entries; the PE accepts them.

In development
F

Change estimates and closeout

Change estimates drafted from what the field already logged, with every line traced to its source.

Planned
C-3 Run the job

The foreman talks. The hours land on the right code.

A note at the end of the day becomes production, delays, material requests and schedule handoffs, each shown beside the words it came from. Nothing is saved until a PE accepts it.

Concept prototype on invented data. Not live yet.

Set manhole 3, base and two barrels. Ran out of grade rings, need six of the 2-inch ones before we can set the cone.
G-1 Why this exists

Built from the trench side of the job.

Zemin was started on the project engineering side of a self-perform underground contractor, watching good people lose hours to tools that don't talk to each other. What PEs said, paraphrased:

  • The estimate gets re-keyed into job costing, and numbers get lost in the handoff.
  • Nobody updates the schedule, because the tool is too hard to keep current.
  • Hours get coded to the wrong code, and someone fixes it by hand in production review.
  • When a person leaves, what they knew about the job leaves with them.

Zemin is the answer. Deep on one trade before it goes anywhere else.

P-1 The pilot

Run a pilot. Free while we build it with you.

Looking for a few self-perform water, sewer, storm or gas contractors in the Bay Area. Everything below is set out in a written agreement before any data changes hands.

You give

  • Closed jobs: budgets, schedules, takeoffs
  • Sample daily reports and time cards
  • An hour a week of a PE's feedback

You get

  • Zemin free for the whole pilot
  • Your cost codes and formats set up for you
  • A direct line to the team building it

We never

  • Share or sell your data
  • Show your numbers to another contractor
  • Keep your data after you ask us to delete it
F-1 Questions
Does it replace HCSS?

Not on day one. Zemin starts with the build: one cost code across budget, schedule, takeoff and field. Your estimating stays where it is until Zemin has enough of your own job history to earn it.

Does it work offline in the trench?

The field app is being built to work offline and sync later. That is required before any field trial.

Who sees our data?

Your company only. Every record is scoped to your company, and pilot data is covered by a written agreement.

Does it run payroll or accounting?

No. Zemin hands clean, coded, approved hours to whatever payroll and accounting system you already run.

Does the AI decide anything on its own?

No. It proposes entries and shows the exact words each one came from. A PE accepts, edits or rejects every one.

What does it cost after the pilot?

One flat monthly price per company with every user included, no per-seat fees. Pilot contractors help set it.