Move every job from bid request to clean closeout.
Zhinova captures new work, keeps schedule handoffs visible and chases the documents and punch items that slow a finish. Your team stays accountable. You keep control of scope, cost and the call.
Made for field reality: messages, photos, changing dates and the next person who needs to act.
Bid to closeout
Closeout movingPunch photo received. Vendor document still open. Owner named.
Where margin gets noisy
Jobs rarely stall because nobody cares. They stall because the next move is unclear.
A bid needs one more photo. A delivery changes the schedule. A punch item is “done” in a text but has no closeout proof. Zhinova keeps those handoffs explicit.
BID
A request arrives without enough to price
The missing scope, photos and timing should be requested before the lead goes cold.
NEXT
The schedule changed but the handoff did not
Every affected person needs the new sequence and a clear next action.
DONE?
Punch and closeout live in scattered threads
Completion means evidence, acceptance and the required documents—not just “handled.”
Three connected workflows
Intake to schedule to closeout.
The system turns each handoff into an owned next action and shows you the few places where a decision is blocking the job.
01
Bid and intake
Capture the request, collect approved scope details and photos, schedule the next step and make incomplete intake visible.
Outcome: cleaner work enters the pipeline02
Schedule and handoffs
Track prerequisites, delivery changes, crew or vendor confirmations and the next trade expected to act.
Outcome: fewer silent dependencies03
Punch, documents and closeout
Assign punch items, request completion evidence and surface missing vendor paperwork before the finish drags.
Outcome: “done” has a definition
Your morning brief
Every open job shows the blocker, owner and next move.
Start the day with one message from Zhina in your chat—not a scavenger hunt through texts, inboxes and yesterday’s notes.
Sample: Zhina's morning brief in your chat
Z
ZhinaYour team manager · Grok Bot chat
Today
Z
Zhina7:30 AM
Here’s your morning brief. Nothing has gone out. Everything below is waiting on you.
Follow-up drafts ready for your OK
Jamie Sample (kitchen bid request) hasn’t sent scope photos yet. I drafted a friendly follow-up.Next step: read the draft and give your OK.
Client update for the 7 Sample Rd. bath remodel Tile is done and fixtures are next. The update includes today’s photos.Next step: review it and OK it.
Replies that need your voice
Robin Example (current client) asked about adding a pantry. Scope and price are your call, so I didn’t draft an answer.Next step: call them. Their notes and photos are pulled together for you.
Dates coming up
Cabinet delivery for 7 Sample Rd. Delivery moved to Tuesday, which affects the install schedule.Next step: approve the new order of work.
Punch walk at 22 Example Ave. on Friday One vendor document is still open for the job file.Next step: OK the reminder I drafted for the vendor.
Tell me which drafts look good, or what to change.
Reply to Zhina…
Sample names and details. Your brief is set up around your work, your language and your approval rules.
Human control is non-negotiable
The system tracks and chases. The contractor makes the call.
Zhinova can keep routine coordination moving, but scope, safety, cost, change orders and client conflict stay with the accountable professional.
✓
Routine confirmations and document requestsRuns from approved templates and timing
→
Stalled dependency or missing proofEscalates with the job context attached
●
Scope, safety, cost or change orderAlways waits for a person
How installation works
Build around how work actually enters and leaves the field.
STEP 01
Map one job path
We trace the messages, documents and decisions from the first request to the completed handoff.
STEP 02
Name every stop
We define the owner, required evidence, reminders and the decisions that cannot be automated.
STEP 03
Test it in the work
We run real scenarios, tune field-friendly updates and expand after the handoffs prove dependable.
About Zhinova
Construction experience is in the room.
Zhinova is built by Chicago operators Derek Light and Lori Wyatt. The experience behind the system includes a Managing Broker, a Chicago GC and 140+ flips/renovations. Lori is a principal of Real Estate Growth Partners and President of the South Side Builders Association (SSBA).
Offer & cost
Clear offer. Locked provisional pricing.
For residential general contractors who need bid/job intake → schedule and open items → closeout notes so the job file stays complete.
What you get
Bid and job intake — capture the request and missing details before the lead goes cold.
Schedule and open items — handoffs, confirmations, and blockers stay visible.
Closeout notes — punch evidence and documents so the job file stays complete.
Included in The Zhinova Team ($499), with 3 months of updates included, then $129 a month for ongoing updates. The Zhinova Team + Setup is $1,497 and adds a live setup call. You’ll also need the new X Premium plan (about $30/mo) from x.ai/pricing, paid by you on your own account. It’s separate from Zhinova and isn’t billed by us. You keep judgment, money, negotiation, and anything that leaves the building. Not included: unsupervised emails/texts, ad spend, replacing your CRM/PM software, or a bot negotiating for you.
Does this replace our project management software?
No. Zhinova can work with the tools you already use. It focuses on the follow-up and open-item desk that often lives between systems.
Can field updates come in through the way our team already works?
The workflow is designed around your real channels and habits. During mapping, we determine which inputs can be captured reliably and where a simple change would make the handoff stronger.
Will it approve bids or change orders?
No. Zhinova can collect missing information and prepare the decision context. Cost, scope and change-order approval remain human decisions.
Can we start with punch and closeout only?
Yes. A bounded workflow with clear completion evidence is often an excellent place to begin before connecting earlier job stages.
Make the next move explicit
Bring us the job handoff your team keeps rebuilding from messages.
We will map where it starts, what proves it moved and exactly where a human decision belongs.
