Skip to content
Our lab · Behind the scenes

Our first client is us.

Before rolling Odoo out for you, we did it for ourselves. Everything you see on this site — quotes, credits, tickets, contracts, payments — runs on our own Odoo, built from A to Z.

Start a project ➔ See client stories
The stack Odoo 19 Python OWL XML / QWeb PostgreSQL Stripe REST / JSON-RPC Linux · Nginx
The starting point

Running an integration business is a craft of its own.

Estimating, invoicing, tracking tickets, signing contracts, getting paid… at the start, everything was scattered. So we did what we do best: we built it in Odoo.

✗ Before

Credits tracked by hand

No way to see who has what, what expires, what remains. A source of errors and disputes.

✗ Before

Tickets everywhere

Emails, messages, spreadsheets… no clear view of progress or of the estimate.

✗ Before

Manual quotes & contracts

Documents rebuilt every time, signatures scattered, payments collected by hand.

What we built for ourselves

A complete platform, built to fit.

Each block answers a real need — and shows what we can build for you.

Customer portal

OWL · Portal
app.gloobal.io · Dashboard
Credits
12
Tickets
3
Delivery
D+4

A workspace where the client follows tickets, credits, invoices and the contract — in one place.

Tickets on a kanban

Project · Workflow
app.gloobal.io · Tickets
To approve
#T-1042
Stripe connector
◆ 6 cr.
In progress
#T-1039
Invoice QWeb report
◆ 2 cr.
Delivered
#T-1005
Migration 18 → 19
◆ 6 cr.

Every request becomes a ticket with an estimate, an urgency level and an automatic debit on acceptance.

Credit ledger

Custom model
app.gloobal.io · My credits
Available balance
12 credits
UseTicket #T-1039−2
PurchaseCredit top-up+5
Exp.12-month expiry−2

A real ledger: every movement tracked, balance computed, FIFO expiry at 12 months. Zero ambiguity.

Estimate & debit

Business logic
app.gloobal.io · Ticket #T-1042
Stripe connectorTo approve
Estimated credits3 d
Urgency×2 · 72 h
To debit6 credits
✓ AcceptDecline

We estimate, the client approves, the debit fires — with ×2 / ×3 rush handling and credit advances.

Contracts & documents

QWeb · PDF
app.gloobal.io · Contract
Contract — S00011CPSB-2026
Read & approved

Quotes, invoices and contracts generated in QWeb, in our visual identity, with electronic signature.

Stripe payments

API · Webhooks
app.gloobal.io · Payment
CBCardinstant
SEPASEPA direct debitrecurring
Top-up · 5 creditsCA$2,950

Card or SEPA collection via Stripe, credits added automatically as soon as the webhook lands.

How we built it

Block by block, testable at every step.

The same method we use with you: from the inside out, never a shopfront without an engine behind it.

  • 1
    The credit ledger
    The movement model and the computed balance — the backbone.
  • 2
    The purchase flow
    Native sales & invoicing: invoice paid → credits added, valid for 12 months.
  • 3
    Tickets & debit
    Custom project: stages, estimate, rush levels, debit on acceptance.
  • 4
    Expiry
    A FIFO cron that expires unused credits, cleanly.
  • 5
    The customer portal
    Dashboard, tickets, credits, contract, invoices — all in one place.
  • 6
    Contracts & emails
    QWeb generation in our visual identity, signature, automated messages.

Everything you see here runs on our own Odoo.

If we trust it with our own business, we can build it for yours.

Shall we build the same thing for you?

A free estimate before any payment. Describe what you need, we reply with a clear plan.

Book a call with an expert ➔