// beamstack · production software, engineered from the problem up
That's not a reason to settle for the closest match.
Most software companies start with a product and hunt for problems it can solve. Beamstack flips that — it starts with the problem (the bottleneck, the workflow no SaaS tool quite fits, the process living in someone's head and three spreadsheets) and designs the software around it.
Beamstack is one person: A. Daoudi, a civil engineer who also architects and ships production software. The domain and the architecture meet in one mind — so there's no translation loss, and no kickoff call to learn what a site actually needs.
// 01 — the flip
Sometimes that means assembling proven architecture patterns. Sometimes it means building something genuinely new. Either way, what I ship is maintainable, scalable, and built to last.
// 02 — the edge
I don't learn your domain from a kickoff call. I'm a civil engineer (EHTP) who also architects and ships production software — two rare disciplines in one mind. So when I build a tool for a site, a structure, or a workflow, I already know where the real constraints live. The person who knows the domain and the person who writes the code are the same person — zero translation loss.
You won't get a sales team or juniors learning on your budget. You get the engineer who built it — and who has stood on the site.
// 03 — the operator
A licensed civil engineer and EHTP graduate who fell in love with code. Where others saw a gap between the physical and the digital, I saw a bridge waiting to be built.
Self-taught from the ground up, I architect software the way I design structures — with load paths, redundancy and precision. From structural analysis tools to production multi-tenant platforms, I bring an engineer's discipline to every line of code, and a developer's agility to every project on site. Moroccan-born, building for the world.
// 04 — selected work · software I build and run
The first ERP built around the site, not around accounting.
The chef records one validated quantity from the field — and it feeds both your client billing and your real cost, so you see margin per lot, in real time, from signed contract down to Lot / sous-Lot. 100% web, multi-tenant SaaS.
30 m² of 100 done, but 45% of the lot budget already gone → you're about to overrun. No horizontal ERP gives you that signal.
six roles, one source of truth
engineered to production standard
Generative 4D construction planning — the schedule is produced from the model, not draped over it.
Backed by a design-science research paper formalizing the element-to-activity granularity gap. An academic paper from a vendor is almost unheard-of — it signals rigor, not vibe-coding.
Mainstream 4D BIM is presentational: a schedule authored in Primavera or MS Project, then linked to model geometry object by object, by hand. Planitor inverts that — the schedule is generated from the model.
Full road design pipeline in one command. Topography CSV + alignment TXT in — optimized vertical profiles, cut/fill earthworks, Brückner haul diagrams, A1 plan sheets, annotated cross-sections and a REFT-compliant Excel workbook out. BET-grade DWG/DXF + PDF following French / Moroccan standards. No AutoCAD.
Turn an Excel schedule into a fully interactive Gantt chart in under 60 seconds. Outputs a standalone, offline HTML file — filterable by discipline, searchable, and PNG-exportable at custom sizes via split & download. No Primavera, no MS Project.
// 05 — de-risking one engineer
The honest question a serious buyer asks: what happens if you're not around? Everything below is built so the answer is "nothing breaks." You own the work, and you can hand it to anyone.
Full source, infrastructure and intellectual property transfer to you. No per-seat licence, no lock-in, no hostage code.
Clean Architecture, typed contracts and CI-enforced boundaries mean any competent team can read, run and extend it — not just me.
For public-sector and enterprise procurement, the codebase can be placed in third-party escrow, released to you on agreed triggers.
Optional support and uptime SLA after delivery — observability, nightly backups and incident response already proven in production.
You talk to the person who wrote the code. No ticket queue, no account manager relaying a half-understood requirement.
A live multi-tenant ERP running a real pilot is the track record — not a slide deck. The de-risking is already demonstrated.
// 06 — how I work
The bottleneck, the workflow no tool fits, the process living in someone's head and three spreadsheets.
Proven architecture patterns where they fit — something genuinely new where they don't.
Maintainable, scalable software, built to last — and run.
// 07 — start here
Tell me the bottleneck. I'll tell you what's buildable — and whether the right tool already exists or needs to.