MEETING NOTES · RESEARCH CHECKED 16 SEPTEMBER 2026 · DESIGN UPDATED 18 SEPTEMBER 2026
Open the five-slide deck · Use PDF ↓ in the deck for the latest download.
A concise, approximately seven-minute partnership conversation with Matthias Heim. The two partnership slides are proposals, not existing agreements.
“We are an AI consultancy that also does the engineering. We can take a real business process from discovery through integration, deployment and handover. That lets us complement Lailix when a project needs more hands or specialist implementation.”
Lead with Grupo Lusiaves, then give two concrete examples from the established prospect deck: Guisoft / Officegest — agents connected to the ERP; Touch.aero — AI strategy and engineering. Other approved references: Beepenger (catalogues, agents, automation), FRAMASTUDIO (process automation), GARQ (computer vision and Smart Prospect). Do not claim the airlines Touch serves as direct Capitao.Consulting clients.
Revenue precision: Grupo Lusiaves is approximately a €1bn annual-revenue group. The reported 2025 figure is €940m, not exactly €1bn. This is client scale, not Capitao.Consulting revenue and not a financial outcome produced by Capitao.Consulting. Forbes Portugal; corroborated by Diário de Leiria, 15 April 2026.
The client references and descriptions come from the existing Dvision presentation, src/content/dvision-presentation.ts, with Grupo Lusiaves, Guisoft/Officegest and Touch additionally confirmed by Wilson for this deck. No client performance metrics are invented.
“We can support the full lifecycle. For this partnership, the most useful part is likely agents, integrations, ML, automated delivery and handover. We agree which responsibilities you want to keep and where we add capacity.”
The slide groups our services into Decide, Build and Run. Supporting capabilities are detailed in the current Capitao.Consulting service catalogue. About Capitao.Consulting supports senior-led delivery; the delivery approach supports client ownership, embedded engineering and handover. ML development and CI/CD were also explicitly specified by Wilson. Avoid promising any fixed percentage saving, service level or delivery deadline before scoping.
Commercial packages are a discovery sprint, a scoped implementation and optional ongoing support. The specific scope determines price; do not claim a verified cost advantage over Lailix's present suppliers. To address the original LinkedIn offer of lower-cost delivery, propose comparing a real scoped project and the margin it leaves Lailix.
“For Grupo Lusiaves, we plan an agent that will pursue every open reconciliation item: find what is missing, trace the evidence across systems, investigate discrepancies and carry each case through to verified closure. That means reasoning through connected transactions, incomplete evidence and timing differences. Alongside it, our projects cover ERP support investigation, technical quotation matching and voice agents that take real actions.”
Positioning: these are selected projects at different delivery stages, not a claim that every listed capability is enabled for every client. Emphasise the connected systems, verification and operational boundaries. No customer records, private evaluation scores, invented savings or unsupported performance claims are shown.
“You already deliver AI. We can extend that capacity while you retain the client relationship. We agree scope, acceptance, price and communication before work starts. Your client gets something their team can understand and operate.”
Lailix's current position is enablement and client independence, not advisory alone. Its homepage describes real workflows and cites Brame marketing automation and Meteomatics conversational dashboards. Its enablement approach includes setting up agents, training champions and supporting teams until they are independent. The company LinkedIn page adds strategy, automation and product-management context. Treat its published case-study performance figures as Lailix's own claims; none are reused as Capitao.Consulting results.
Proposed operating arrangement: Lailix is the commercial lead; Capitao.Consulting is a delivery subcontractor or named co-delivery partner. Jointly review the architecture and release. Agree milestone acceptance and change requests. Before delivery, record client-contact rules, confidentiality, code/IP ownership, access permissions, hosting, subcontracting consent and support boundaries. These are commercial discussion points, not signed terms.
Swiss delivery: Lailix offers standard API, EU-hosted and Swiss-hosted tiers in its data-residency proposition. Capitao.Consulting's remote engineering from Portugal does not itself establish Swiss-only data handling. Agree development datasets, remote access and production permissions per client. Do not promise that data never leaves Switzerland unless the entire arrangement supports that claim.
“Beyond overflow engineering, we can take a successful workflow and make it easier to deliver again. Start with one live client opportunity. Define a paid pilot, agree what success looks like, then decide whether repeating it makes commercial sense for both of us.”
Meeting close: “Which current client opportunity would make the best test of working together?” If Matthias has no immediate opportunity, propose one joint qualification session and exchange a relevant demonstration and delivery checklist.
These informed the proposed structures. They are analogies, not Capitao.Consulting or Lailix partners, endorsements or comparable scale claims.
| Published example | What it supports | How to adapt it here |
|---|---|---|
| Teneo + Thoughtworks 16 March 2026 | A joint venture connects executive advisory, business transformation and hands-on AI/software engineering. | Agree a complementary delivery split and shared acceptance criteria. A subcontract or co-delivery agreement is sufficient for a first project; no joint venture is needed. |
| BCG + Anthropic 4 June 2026 | An initiative combines BCG expertise with Anthropic model access and hands-on training for social-impact organisations. | Bundle technical implementation with client capability transfer. Match contributions to the outcome instead of selling engineering hours alone. |
Capitao.Consulting uses the official transparent stacked logo export from its current brand assets. Capitao.Consulting and Lailix appear together at a small size in the upper-right corner of every slide. Lailix retains the exact logo file linked by its live website, with its original white-and-gold lettering and navy background; the two-pixel outer border is clipped in CSS. Every slide uses the matching navy background (#0d1f2d).
Customer and project logos use original artwork with transparent backgrounds: Lusiaves's white group logo from its website footer; Guisoft's basic red logo from the existing proposal assets; Touch.aero's multicolour logo from its homepage; Beepenger's white logo from the project brand assets; and Atendedor's original yellow sound-wave mark shared by its homepage, application and favicon. Lusiaves and Touch.aero assets were checked byte-for-byte against their current website originals. Logos are embedded without recolouring or redrawing; transparency, loading, placement and PDF rendering are checked. Atendedor remains a project/platform example, not a separate customer endorsement.
18 September project examples: a fifth slide was added after services using the established column layout, navy background, official logos, large type and staggered entrance reveals. It now contains four examples, led by the planned Grupo Lusiaves reconciliation agent requested by Wilson. The planned investigation and closure workflow is distinguished from the existing deterministic reconciliation foundation. Project capabilities and delivery-stage limits were checked against current project documentation. The four-slide Claude reviews described below predate this addition.
18 September simplification: Claude Code Fable 5.1 at xhigh reviewed the previous slides and recommended one headline and one supporting group per slide, a three-part Decide / Build / Run service layout, less navigation chrome, and a prominent paid-pilot ask. These recommendations were applied. A second Fable 5.1 xhigh review of the new slide images concluded that the deck meets the brief. Its final refinements were applied: explicit client labelling, aligned columns, consistent navigation numbering and a shared client-ownership statement beneath both partner roles. Detailed delivery terms and additional client references remain in these notes. Entrance animations reveal each group briefly; slides never auto-advance. Reduced-motion mode disables movement and the PDF shows every element.
Claude Code CLI was invoked with model claude-fable-5-1 and effort xhigh to critique content and design. The content review prompted stronger emphasis on handover, client independence and Lailix account continuity. Fable then inspected all four rendered slide images and found the layout clear, with no content overlap or crop. Its final recommendations were implemented: add specific client work to slide 1, separate the pilot acceptance wording, improve Lailix logo contrast on the dark slide, and shorten the footer near the controls. Its suggestion to guarantee Swiss-only data handling was not adopted because that needs a client-specific architecture and access agreement.
Use arrow keys, Page Up/Down, Space, the on-screen buttons, or swipe. Home and End jump to the first and last slide. Controls fade after inactivity and reappear with pointer, touch or keyboard input. PDF contains exactly the five presentation slides; these notes stay separate.
Scheduling note: the supplied LinkedIn exchange confirms Wednesday 16 September at 10:00 Swiss time. The slides intentionally contain no meeting date. No invitation or message was sent.
