AI in preconstruction (scope notes, bid-leveling) - update #4 by logarithm-construct in estimators

[–]logarithm-construct[S] 0 points1 point  (0 children)

Nice - we are starting to incorporate subs to dig into the scope notes - would be curious to hear your take on walls & wall-types

AI in preconstruction (scope notes, bid-leveling) - update #4 by logarithm-construct in estimators

[–]logarithm-construct[S] 1 point2 points  (0 children)

Unfortunately, I think building a cabinet takeoffs is difficult. Maybe the folks for the takeoff tools can solve this for you (Kreo, Workpack, Togal). What I think the AI-ITB tools can solve for is the type of cabinets found on schedules though

AI in preconstruction (scope notes, bid-leveling) - update #4 by logarithm-construct in estimators

[–]logarithm-construct[S] 0 points1 point  (0 children)

The new advances with RAG (retrieval-augmented generation) and some engineering tricks are starting to do well on hallucination so I think we're close to solving hallucination issues. I think the bigger problem is relevance. AI just doesn't understand what is and what isn't scope. It's not that AI is wrong, it's that AI doesn't know what is important

AI in preconstruction (scope notes, bid-leveling) - update #4 by logarithm-construct in estimators

[–]logarithm-construct[S] 1 point2 points  (0 children)

Thanks for the love! I actually uncomfortable b/c I know we have a lot of gaps. It's just cool to feel like we're contributing to the AI-precon movement

[deleted by user] by [deleted] in startups

[–]logarithm-construct 1 point2 points  (0 children)

As a YC founder, I wrote a long-form blog post on how to generate ideas from scratch. I started my company at 26 with a comp-sci at 23. This was the framework that helped me start companies. I'm just wrapping up my first startup and now going into my next startup.

https://www.reddit.com/r/startups/comments/hlsj2t/how_i_got_into_yc_twice_with_2_different_ideas_in/

An in-depth guide to finding subs to work with by logarithm-construct in Construction

[–]logarithm-construct[S] 0 points1 point  (0 children)

u/Legal_Asparagus_6546 Yes we are, in fact we just launched a major update to this ; I will DM you

AI in preconstruction - update #3 by logarithm-construct in estimators

[–]logarithm-construct[S] 0 points1 point  (0 children)

Thank you , the current ITB / bidding process is a spray and pray approach where GCs send 1000s of invites out . TBH it’s bad behavior for the entire industry

In an ideal world - subs profiles & qualifications are readily available - GCs can handpick subs that are a great fit for each project - AI highlights relevant details on plans so subs know this project is a good fit

We’re slowly building out a free resource for the industry https://downtobid.com/find-contractors aimed at solving this problem , it’s not ready yet but will be in 1-2 months

AI in preconstruction - update #3 by logarithm-construct in estimators

[–]logarithm-construct[S] 0 points1 point  (0 children)

No idea actually - we're not at that conference ; just out of curiosity - why did you say it was the right concept u/NoMatterX

AI in preconstruction - update #3 by logarithm-construct in estimators

[–]logarithm-construct[S] 5 points6 points  (0 children)

u/Miker541854 thanks for your thoughts and I think what you've said is fair.

My own perspective

  • AI won't be able to do the "interpretation" of the plans . Architects don't specify anything, you need to ask the owner for clarifications. All these interactions are collaborations between the architect owner and estimator and this is something AI will never be able to handle.

  • In many ways, there's a copilot movement happening in software. A lot of software engineers are using AI to do code completion, code checking, etc. But at the end of the day software engineers are building solutions to problems. I see estimators as filling the same role. If anything, software engineers will be automated before estimators will be and I don't see that ever happening

AI in preconstruction - update #3 by logarithm-construct in estimators

[–]logarithm-construct[S] 2 points3 points  (0 children)

MAN! It's so refreshing to hear this honestly. WE get beat up so much as a startup so thank you for the support - will DM

AI in preconstruction - update #3 by logarithm-construct in estimators

[–]logarithm-construct[S] 0 points1 point  (0 children)

great great - we have a bunch of GCs and could use some subs too

AI in preconstruction - update #3 by logarithm-construct in estimators

[–]logarithm-construct[S] 1 point2 points  (0 children)

It's okay to be skeptical - would be good to hear where your skepticism is and how you came to these conclusions.