Excibat_

From the start of the mission in July 2025, the first challenge was to map the documentary complexity of construction: amendments, Final General Statements (DGD), progress invoices, Acceptance Reports (PVR) and Reservation-Lifting Reports (PVLR). Each document follows strict approval statuses and engages the signatories’ legal liability.

Technical exploration quickly exposed the weight of Oodrive’s “all-in-one” API and its submission mechanisms. I architected the API calls and two-way webhooks to trace signature progress in real time, automated VAT rate updates, synchronised e-mail reminder loops via SendGrid and conditioned document access on each user’s status in the project.

• Oodrive Sign API foundation & webhooks
• Automatic SendGrid loops
• Signature flow matrix
• Bubble debt audit

In autumn 2025, we extended the web app towards autonomous SaaS operation. I designed and documented the subscription funnel for the annual plan (paid monthly) through Stripe Checkout, adjusting the architecture so payment does not require creating an account first.

In parallel, the product gained services that are directly useful in the field: Météo-Concept API integration to show 14-day forecasts geolocated on each site, bulk download of tender documents and data deletion management at the end of the Perfect Completion Guarantee (GPA). During the late-November review, in-depth ergonomic work was done on global navigation to guide users step by step and fix critical status anomalies.

• Stripe Checkout & Billing funnel
• 14-day site weather API
• Bulk tender-pack download
• Phase-guided navigation

In December 2025, a major structural finding made the product pivot: an architect or an engineering office works on sites for several different developers, and the same subcontractor works for several organisations at once. The original Bubble model, designed for a single closed organisation, was becoming a dangerous bottleneck for data security.

In March 2026, I led the multi-organisation migration in 6 phases. Architecture: strict distinction between the principal organisation and the contributing company. Data migration: lossless reassignment of project history and move of SIRET / VAT attributes to the organisation. Security & Privacy Rules: since Bubble cannot compare two lists in its Privacy Rules, access control was moved into backend workflows that compute explicit lists of authorised people.

Workflow refactoring: project creation, notifications and cascading deletions adapted to eliminate any “ghost” orphan relationship. Transparent interfaces: complexity absorbed behind the scenes, with a deliberate refusal of a visible organisation selector. Multi-account acceptance: cross-validation protocols in test and pre-production.

• 6-phase migration plan
• Organisation ⇄ Company model
• Privacy Rules moved to backend
• Zero-loss migration scripts

Excibat’s validation relies on close collaboration with Francis, who is at once sponsor, domain expert and user on his own property operations. His feedback corrected theoretical design mistakes. Manual vs automatic closing: in a construction tender, submitting a bid does not close the file, technical and financial negotiation continues; automatic closing was therefore replaced by a concerted manual action.

Ergonomics adapted to construction: faced with interfaces judged too clean for building professionals’ landmarks, the UI evolved towards more framed, structured and contrasted screens, with a strong identity (signage green, bold typography, historic EB logo kept). Client autonomy: so that Francis does not depend on a contractor for every adjustment, I built a centralised admin page (batch management, technical checks) and documented every workflow.

Work continued on making payment certificates reliable (responsive behaviour and progress statements) and on marketing positioning focused on GPA management.

• Centralised admin console
• Payment certificates & progress statements
• Workflow documentation