Skip to content

Model

From your first message to a decision in writing.

Every request starts the same way: you tell us what you're working on, and we find the way of working that fits before anyone talks about scope or price. So the meeting you get is prepared for your product or business, not a discovery call from zero.

Write through the form or talk to Oliver, our AI assistant. A manager replies within one working day, usually with a Google Meet invitation for a 30-minute introductory conversation.

What happens after you write to us

  1. 1

    Your situation

    You describe what you are working on; we identify the route before anyone talks about scope.

    What you get
    A working conversation about your situation; we do not pitch.
    Risk removed
    Months in the wrong engagement model.
  2. 2

    First conversation

    A 30-minute introductory conversation to see whether the opportunity is a fit for assessment.

    What you get
    A clear answer on whether it goes further.
    Risk removed
    Paying for discovery before the basics are checked.
  3. 3· Up to seven working days

    Assessment before development

    We check the market, the product and the commercial logic internally, before any development is discussed and without committing either side.

    What you get
    The Build Decision: proceed, reshape or decline — in writing, with reasons.
    Risk removed
    Building a product whose logic does not hold.
  4. 4

    Build Decision

    The Build Decision — proceed, reshape or decline — before any code. The CEO makes it and gives the reasons in writing.

    What you get
    A decision owned by a named person.
    Risk removed
    Committee ambiguity and silent drift.
  5. 5

    A meeting prepared for you

    A meeting prepared for your product or your business: structure, responsibilities and commercial terms, prepared in advance and confirmed in writing.

    What you get
    Terms you can decide on.
    Risk removed
    Open-ended scope.
  6. 6

    Build and operate

    Development starts only after the meeting and written terms. We build to operate: launch is one stage of the work, and running the product is the rest.

    What you get
    One accountable operator across the lifecycle.
    Risk removed
    A handover to nobody.

When we decline

We decline when the product logic does not hold, when the commercial model cannot support operation, or when we could not take responsibility for the outcome. A decline is a decision, not a delay, and we say why.

What the Build Decision is, in detail

Two core operating models

Product PartnershipAnnual Product Operations
ForA new standalone digital productAn existing company whose digital operations must work as one system
EntryFirst conversation → assessment → Build DecisionIntroductory conversation → offer prepared for your business → process review and yearly roadmap in months 1–2
Commercial modelDefined for each partnership after the Build Decision. Equity is not automatic.A yearly programme, paid monthly: equal instalments tied to the roadmap, not to hours
HorizonFrom validation to launch and operationTwelve months, renewed on results
Decision meetingA partnership meeting, prepared in advanceAn offer meeting, prepared in advance
CapacityUp to ten partnerships a year; no more than five in development at any one timeUp to fourteen programmes in parallel
Shared risk and upside

In a Product Partnership we carry part of the product risk with you: the assessment, the Build Decision and the prepared meeting come before any development, and in selected partnerships we may participate in agreed upside or ownership under a written commercial structure.

Equity is not automatic

The commercial structure (a fee, equity or a combination) is defined for each partnership after the Build Decision and confirmed in writing. In Annual Product Operations and other client-owned engagements, ownership and IP stay as the written agreement defines them.

Capabilities behind the work

The capabilities below are not sold as disconnected commodity services. They are combined according to the selected route, agreed scope and required product or business outcome.

  • Product strategy and validation

  • Business analysis

  • Product and system architecture

  • UX/UI and product design

  • Engineering

  • AI and automation

  • Data and reporting

  • Quality assurance and delivery control

  • Launch and product operations

Not a fit if…

If that is you, an agency or an AI app builder will serve you better. We will tell you so on the first call.

  • You need a fixed-scope build from a finished specification, with no product decisions to make.
  • You want to buy developer hours by the day.
  • You expect a guaranteed commercial result or a guaranteed grant.
  • You need a prototype by tomorrow and nothing has to run after that.
  • You need the cheapest possible quote.

We enter each product as our own.

  • Product Partnership

    We open up to ten Product Partnerships a year and keep no more than five in development at any one time, because we enter each product as our own.

  • Annual Product Operations

    Up to fourteen annual programmes run in parallel, never more, so each one keeps a named owner and a monthly rhythm.

  • Funding & Grant Support

    We prepare six applications a year, two per funding cycle, so every application gets real preparation time.

  • Referral Program

    Qualified introductions are always welcome.

Logics7 operates with access to 350+ specialists across product, engineering, AI, design, quality assurance and delivery, so delivery capacity scales. The Build Decision — proceed, reshape or decline, taken by the CEO before any build — does not. That is the real limit.

Tell us what you're working on.

A new product, a business process, a live product, a grant application or an introduction — a few lines are enough to find the right next step.

We reply within one working day.

Which route fits you? →