A single project
A defined piece of work, such as a campaign plan, creative production or research study.
Know what happens before the work starts.
LGM begins by defining the goal, inputs, deliverables, responsibilities, costs and review points. The exact process then fits the type of work.
Bring an early idea or a clear brief.
Tell us what you want to make, understand or improve, what is not working and what you already have. You do not need to choose every service before contacting us.
A build
Software, an integration or an AI workflow with agreed requirements, tests and handover.
Ongoing support
Continuing work with a defined scope, review rhythm and responsibilities.
A combined scope
Services planned together when the work spans more than one capability.
FROM DISCUSSION TO HANDOVER
A process shaped around the work.
These stages explain the general approach. Your proposal sets the actual deliverables, milestones, review points and responsibilities.
- 01
Understand the goal
We discuss the question, audience or task, the current situation and any important constraints. Existing work, available information, budget and timing help shape the next step.
- 02
Define the approach
We identify the relevant capabilities, inputs and access, likely deliverables and important limits. Where several services connect, we clarify how they fit together.
- 03
Agree scope and terms
The proposal or agreement records the work, responsibilities, fees, external costs, milestones and review points. Rights, confidentiality and data-processing terms are addressed where relevant.
- 04
Deliver and review
Work moves through the agreed stages. The relevant people review drafts, findings, creative or working software, with feedback and approvals handled through the agreed process.
- 05
Check and accept
We review the work against the agreed deliverables and acceptance checks. Issues, revisions and proposed additions are assessed against the scope before the next step is agreed.
- 06
Hand over and plan support
We provide the agreed files, documentation, access and rights information. The agreement identifies who runs or maintains the work after handover and whether ongoing support is included.
What your proposal may include.
The detail depends on the project. These are the points to settle before paid work starts.
- The goal, included work and exclusions.
- Deliverables, formats, milestones and client dependencies.
- Responsibilities, required access and named reviewers.
- Agency fees, taxes and separately identified external costs.
- Review rounds, approval steps and acceptance checks.
- Ownership, licences, account control and handover.
- Confidentiality and personal-data processing where relevant.
- Scope changes, cancellation, maintenance and support terms.
What we need from your team.
Useful starting inputs include your goal, audience, existing materials or systems, practical constraints and preferred timing. The project may also need authorised account access, reliable source information, rights to supplied material and people who can review the work.
Do not send passwords, identity documents, sensitive personal data or confidential datasets through the public enquiry form. Agree the scope and a suitable sharing route first.
Keep costs, changes and reviews clear.
Know which costs are separate
Agency fees are separate from advertising spend, creator payments, research incentives, software, AI usage, telecom charges and other external costs unless the written proposal says otherwise.
Agree changes before extra work
If requirements change, we assess the effect on deliverables, cost, timing and dependencies. Additional scope or spending needs the agreed approval. Silence does not automatically approve a change.
Set useful review points
The project sets who reviews the work, when feedback is needed, which revisions are included and how acceptance is checked. A correction to agreed work and a new requirement are assessed separately.
Know what you receive and what happens next.
The agreement identifies final deliverables, any editable files or source code, documentation, account control and usage rights. Existing tools, third-party assets, code libraries and platform services may carry separate licences or restrictions. Maintenance and support are defined separately where they are not included.
Before you get in touch.
Do I need a complete brief?
No. Start with the question, task or problem and what you already have. We can discuss which capability is relevant and what needs to be clarified before a scope is agreed.
Can I start with one service?
Yes. You can discuss a single project, a build or ongoing support. Services can be combined when the work calls for it; you do not need to buy every capability.
What determines price and timing?
Scope, complexity, production volume, research method, integrations, access, review needs and support can affect the proposal. We confirm fees and schedule for the agreed work and identify external costs.
Does an enquiry start a paid project?
No. An enquiry does not create a paid engagement, reserve capacity or confirm project acceptance. Paid work begins only after scope and terms are agreed.
DISCUSS A PROJECT
Discuss a project Tell us what you want to make, understand or improve.
We can discuss your project and explain how we can help.