01 / READS
Reads your email
Alfred connects to your project email. Every thread. Every attachment. Captured the moment it lands.
AlfredAlfred reads your project email 24/7.
So you don't have to.
Alfred is an agentic project manager for construction. He reads every email, every drawing, every RFI, every submittal, every schedule. He catches what slipped before it cascades. He drafts the follow-up. You approve.
You're drowning in communication.
400 emails a day. RFIs buried. Submittals stuck. A sub mentions a delay on a call — and if you don't catch it, nobody does.
You're not managing one project. You're carrying the communication system for the entire job.
Procore stores it. P6 displays it. Neither one does the work.
So the project lives where it always has. In your head. In your inbox at 11 PM.
This is the job.
It should not be the job.
Here's what Alfred does, today, on a real job.
Not a roadmap. Not a vision. What is running right now.
02 / READS
Reads your documents
Drawings, RFIs, submittals, contracts, and schedules. Alfred reads them like a senior PM who does not get tired at 6 PM.
03 / FINDS
Finds the open loops
Who asked for what? Who owes an answer? What got mentioned once and never followed up? Alfred keeps track.
04 / ROUTES
Drafts the follow-up
When a delay, question, or missing approval appears, Alfred drafts the message to the right person. You approve before anything goes out.
Under the hood.
Here's what's actually happening.
01
How Alfred reads documents.
Drawings are rotated. Schedules sprawl across pages. RFIs reference older drawings. Contracts hide risk in language nobody has time to reread.
Alfred reads them anyway. He pulls type codes off luminaire schedules, traces conduit runs across rotated PDFs, and surfaces the clause on page 47 that’s about to cost you money.
The documents stop being documents. They become a project model.
02
How Alfred reads communication.
Construction email is where decisions go to die. Three people CC’d, nobody owns it, the answer’s in a forwarded thread from Tuesday.
Alfred reads the way a senior PM reads — between the lines. He resolves who “Mike” is across 14 threads, tracks which RFI was actually answered, and notices when a sub commits to a date and then quietly walks it back.
Alfred reads construction email like someone who’s been on the job.
03
How Alfred connects email to the schedule.
A Gantt chart is a snapshot from a meeting that already happened.
When an email lands, Alfred maps it back to the schedule. A delivery slip becomes a delayed activity. A delayed activity recomputes float. Recomputed float surfaces every downstream trade about to be impacted — before the impact happens.
The schedule stops being a document. It becomes a model.
04
How the human stays in the loop.
Alfred drafts. You approve. Always.
When Alfred sees a problem, he prepares the response — message, recipient, options, cost. Nothing goes out until you click send.
Alfred sees what’s coming. You decide what to do.
What Alfred is becoming.
Forecasting.
When one trade slips, Alfred models the cascade across every dependent trade. What shifts. What breaks. What it costs.
Accountability.
Every decision. Every approval. Every commitment. Captured, timestamped, and connected to the person who made it. No more digging through 400 emails to find the one sentence that mattered.
Autonomous routing.
The communication bottleneck starts to disappear. The project executive stops being the human switchboard. The PM stops being a clerk. The team gets back to running the job.
See it for yourself.
The best demo isn't a video. It's you emailing Alfred and watching him email back.
Take Alfred for a ride.
Thirty minutes. One Zoom. You email Alfred. He emails back.
01
The first 5 minutes
You tell us what’s bleeding on your current job.
02
The next 20 minutes
You email Alfred. Ask him what’s open. Send him a delay. Try to break him.
03
The last 5 minutes
We talk about whether Alfred fits your job. No pitch. No deck.
No project data needed. No NDA. We use a sample job.
Who's building Alfred.
Pejman Golkar — PJ
FOUNDER
25 years across high tech and construction. Building Alfred because the projects he has worked on deserved better than database-and-chart software. Based in Los Angeles.
Todd Pennington
CO-FOUNDER
40 years in construction. Over $22 billion in projects delivered, zero claims. Todd is the reason Alfred is being built for how the industry actually works — not how Silicon Valley thinks it works.