Guide
From the Build Decision to a signed agreement
Five steps between your first message and a signed agreement. Each has a time limit or a document, and everything is set out in writing before any build.
Five steps
- Reply. A manager replies within 4 working hours, usually with a Google Meet invitation for a 30-minute introductory conversation.
- Introductory conversation. Nothing confidential is needed for a first conversation: the problem, the user, the business logic and the stage are enough.
- The Build Decision. Proceed, reshape or decline — in writing, with reasons, within 48 hours on working days. Before any code.
- Offer meeting, within five working days of a proceed. If we proceed, a manager presents a prepared commercial offer and the recommended way to work together.
- Agreement. Nothing is agreed before the Build Decision. If we proceed, your payment, the 30% stake (you hold 70%), the new company and the publishing contract are set out in writing before any build.
If the answer is reshape or decline
Then you hear it before you spend on development: the Build Decision comes in writing, with the main reasons. The letter is yours to keep. If we decline, you can take it to anyone you like.
We do not take every idea into development.
What is set out in writing
Scope, roles, budget, IP, milestones, acceptance criteria and the commercial structure, in writing.
In a Product Partnership, Logics7 takes 30% of the new company that owns the product, for the development it adds on top of your payment; you hold 70%. The terms go into the shareholders’ agreement before any build.
Take the documents to your lawyer before you sign.
Questions
Tell us what you're working on.
New product, business process, live product, grant or introduction: a few lines are enough to find the next step.
Anton replies within 4 working hours. The form opens with this route already selected. Prefer a call? Request a callback