Partnerships
Shape your partnership.
We don’t sell one package. We agree the shape first, then write the contract around it. A partnership can combine models, and move from one to another as it grows.
Settled in writing, whatever the shape.
The rest is detail, and we write it down before we start.
Which entity runs the work
- 01Our registered company, contracting with you directly
- 02Your entity, with our team contracted into it
- 03A new company set up for the partnership, with ownership split as agreed
Where the team sits
- 01In our office in Tripoli
- 02In an office we find and set up for you
- 03Fully remote, with our management keeping the team together
Whose cloud accounts
- 01Ours: the fastest start, billed at cost plus an agreed fee
- 02Yours: we manage them, and you hold the billing and the keys from day one
We can also reserve a defined share of our engineering capacity for you, over a fixed period.
Fixed in every partnership.
Confidential by default
A mutual NDA comes first and stays in force after the engagement ends. Everyone we assign to your work signs an individual NDA and an IP assignment.You own what you pay for
What we build for you is yours once it is paid for, assigned in writing. Our pre-existing tools and frameworks stay ours, and you get a perpetual licence to use them inside your product. Open-source components are listed with their licences.Your data stays yours
We process it only to deliver the agreed work. On exit, we hand it over in an agreed format and delete our copies.Nothing held hostage
Who owns each account, domain and repository is written down at the start. You can take the team in-house after an agreed notice period.Secure by process
Code review, dependency scanning, secrets kept out of code, least-privilege access and audit logs on production.No silent extras
A change that affects price or timeline is written down and approved before we build it. Defects in delivered work are fixed at our cost within the warranty period.
How an engagement starts
- 01Intro callWhat you’re building, and whether we’re the right fit.
- 02Mutual NDASigned before any technical detail is exchanged.
- 03Discovery, 1 to 3 weeksA written scope, an architecture outline, a timeline and a price. You own this output, even if you don’t continue with us.
- 04ProposalScope, shape and price.
- 05AgreementSigned by both sides.
- 06Delivery, in cyclesOne decision-maker on each side, a weekly call, and a written update on what shipped, what’s next and what’s blocked.
Questions
Can we start with one model and change later?
Yes. A partnership can combine models, and move from one to another as it grows.
Can we take the team in-house?
Yes, after an agreed notice period, under terms set at the start. We do not hold a team hostage.
Who owns the code?
You do, once it is paid for, assigned in writing. Our pre-existing tools stay ours, with a perpetual licence for you to use them inside your product. In a joint product or a new venture, ownership is set in the shareholders’ agreement instead.
What if work in Lebanon is disrupted?
Delivery doesn’t depend on one office. Teams can work fully remote, your product can run in cloud accounts you own from day one, and code, documentation, credentials and data are handed over in an agreed format, under terms set at the start.
Do you take equity?
Sometimes, when we believe in the product. It is decided case by case, alongside cash or instead of it.
Not sure which shape fits?
That’s what the first call is for. Tell us what you’re building, and we’ll suggest one.