We're genuinely excited.
If you bid to get jobs, send us a closed-out bid that you and your team previously prepared, and we'll send you back the full package made by Mebbian.
#aec#constructiontechnology#mebbian#architecture
Mebbian is now a member of NVIDIA Inception!
Here's what we're building: the Bid Engine for construction and architecture teams.
It prepares the full bid package from your own drawings, specs, past bids, and historical project knowledge. Your team reviews every line and makes every call.
If you bid work: send me one job you already bid. We send back the full package, free. You already know how that job ended, so you grade us.
DM me!
Day 3 of SF Tech Week.
One thing is becoming clear: being surrounded by people building ambitious things changes the way you think about what’s possible.
Between founder conversations, AI events, and getting Mebbian in front of new people, this trip has been worth every minute.
And we’re just getting started.
Mebbian @Techweek_
Mebbian is now a member of NVIDIA Inception.
We build a private AI memory for construction and architecture firms, so every estimate starts from the jobs they've already run.
@mebbian just got into NVIDIA Inception!
Flew to SF Tech Week on a bet. Stayed in Berkeley. Spent 15-hour days going to events and having cold conversations.
It paid off before the week was over.
Huge thanks to Deanna and Daniel from Transcripta Bio for putting in a good word.
I WAS QUOTED $3000 FOR THIS!!!
So I asked Opus 5.5 (medium) to create a launch video using Motion Graphics for us.
here's the prompt that one-shots it:
"Create a 15s motion-graphics film explaining {{PRODUCT}}. HyperFrames + GSAP, no voiceover, no footage.
Style: paper-light canvas, marker notes that draw on, real physics, huge kinetic type,
hard light/dark switches, a new idea every 1.5–2 s, a sound on every hit.
COPY: read {{POSITIONING_DOCS}} first. {{ONE_LINER}} For {{AUDIENCE}}. {{WHAT_IT_DOES}}
Name what the product learns, never the abstraction.
RULES
- No chrome (scrubber, timecode, fps, headers). No animator jargon on screen
("squash", "stagger", "easing"...). Every word speaks to the buyer.
- No invented results: no %, multipliers, customer names or figures.
- Never use: {{BANNED_WORDS}}.
- Logo: real mark {{LOGO_FILE}} + "{{PRODUCT}}" in {{WORDMARK_FONT}}; never a boxed logo file.
CRAFT
- Colours {{COLOR_CANVAS}} / {{COLOR_INK}} / {{COLOR_ACCENT_1}} / {{COLOR_ACCENT_2}}; notes in the
accents; dark mode = charcoal matching the palette.
- Fonts {{BRAND_FONTS}}; Anton for kinetic type; Caveat handwriting via stroke-dashoffset.
- Real easing, squash/stretch, stagger, overlap, onion skin, smear, follow-through. Check the
HyperFrames registry first. Set every from-state at t=0 (seek-safe); never cover an exit.
One primary move per transition; no generic push/slide/rotate-swing.
- Music in sections: drums drop on the dark switch and while the ball is airborne, slam back
on the type and the logo. SFX: pops, pen scribbles, whooshes, logo sub-hit. CC0 or generated
only; log sources. Master -14 LUFS, -2 dBTP, re-measured after AAC encode."
@ik_builds The part most firms underestimate is how much of their “standard process” has never actually been standardized.
It lives in corrections, old projects, estimator habits, naming conventions, exceptions, and the judgment of whoever has been there longest.
6% of architects use AI routinely. 51% of contractors are actively evaluating it, 40% already have a budget line for it.
Same building. Same drawing set. Completely different speeds.
(AIA March 2025. Dodge + CMiC, 235 US contractors, late last year.)
everyone's reading that gap as "design is behind." I don't think that's the interesting part.
intelligence is about to be the cheapest thing in the office. $20/seat and dropping. eventually both sides have it and whatever edge came from access just closes on its own.
what doesn't commoditize is the stuff your firm knows and never wrote down.
point a frontier model at a drawing set, it reads text off it at ~95%. symbol understanding drops to 40-55%.
it sees W3 and reads a label. your office knows W3 is a rated partition. specific stud spacing, board, insulation, track, screws, finish. settled years ago. written down nowhere.
same with the waste % you add on board. same with the opening size you stopped deducting below. nobody voted on those. they live in whoever's been there longest.
so every project restarts from zero.
been building toward the opposite. projects that carry a brain. the dictionary, the assembly rules, the conventions nobody documented, sitting with the project instead of with a person.
ask it a number and it links you the page it came from. ask it something the record doesn't support and it just says no.
the refusing part is the part people trust btw. took me way too long to figure that out.
So I made a list of the forty questions that surface all of it. reply "Standards" if you want it.
6/6 This is what the operating layer does. It gives the agent the memory, the rules, and the context to act like someone who actually understands your business. Not automation. Not a bot. A system that operates.
Follow for more.
https://t.co/4LpfAc1V9e
1/6 Here's what it looks like when Mebbian is running. It's 2:14 AM. A founder is asleep. A lead just submitted a form on their site. Here's what happened next.
5/6 At 7:52 AM the founder opened their phone. One new calendar invite. Internal note from the agent: qualified, high-fit, ready for discovery call. The conversation had already happened. The work was already done.
You've explained your business to your AI again and again.
It still doesn't know how decisions get made here. No customers, no constraints, no context.
That's the layer no one built.
We built it.
You've explained your business to your AI again and again.
It still doesn't know how decisions get made here. No customers, no constraints, no context.
That's the layer no one built.
We built it.