Resources · Scoping
Write the scope the way Maxiom actually scopes — before the call.
Problem, stack, regulatory context, access constraints. Output: deliverables, NDA, read-only default, named engineer. Not a sales deck.
Vague RFPs produce vague vendors
Maxiom starts with a 30-minute scoping conversation, then written scope before anyone touches a repository. Teams that show up with a structured outline — problem, stack, constraints, what “done” means — get a faster yes or an honest no. This builder produces that outline in the same shape as our model.
Who this is for
- Buyers preparing a scoping call who want the homework done.
- Internal stakeholders who need NDA and read-only written down before GitHub access is requested.
- Leaders comparing a build, an AI code audit, or CTO advisory and wanting the same outline format.
What you get
- A structured scope: problem, stack, regulatory context, in/out of scope, deliverables.
- Access model in writing: NDA first, read-only default, named engineer if we proceed.
- Copy, print, or save as PDF. Email capture uses the same HubSpot gate as the checklist.
Frequently asked questions
What is the engagement scope builder?
A short form that turns a problem, stack, regulatory context, and access constraints into the outline Maxiom actually uses: deliverables, NDA, read-only default, named engineer. It is a draft for your next conversation — not a contract.
How does Maxiom actually scope work?
A 30-minute call, then written scope before anyone touches a repository. Access is NDA first and read-only by default. The model is on How Maxiom works. This tool is that outline in self-serve form.
Will you email me the outline?
The work-email gate records the request (same HubSpot form pattern as the checklist). Copy and print are available in the browser immediately. A HubSpot workflow can forward the file once Antonio wires the form — the generator does not upload a repo.
Who should use this?
Founders, VPs of Engineering, and procurement partners who want a structured starting point before a scoping call. Also useful internally so legal sees NDA and read-only before anyone asks for GitHub org admin.
Does filling this book an engagement?
No. It produces an outline. Fit still takes a conversation. If we are not the right firm, we will say so.
What if we need fractional leadership rather than a build?
Say so in the problem field. CTO advisory is a different shape (retainer or project) with the same access discipline.
Can this cover AI code audit or oversight?
Yes. Describe the forcing function (questionnaire, fundraise, incident) and the tools in use. The outline will still insist on NDA and read-only before review. Paid snapshot: AI code audit.
Do you need repository access to generate the outline?
No. Repository access happens after written scope and NDA, and only if the work requires it. The builder never asks for a clone, a dump, or production credentials.
Is the named engineer assigned when I click export?
No. The outline states that a named senior engineer will be accountable if we proceed. Assignment happens after fit and written scope — not in a browser tool.
Launch
Launch the builder
Sign in with a work email, then run the tool in this page. Client code stays in your environment.
Work email to continue
Unlock Engagement scope builder
Same gate as the AI Code Risk Checklist. Unlock once per browser session to use or export. Client code stays in your environment — this tool never asks for a repository.
- Questionnaire only — no source upload
- Print or save a one-pager from the browser
- Unlocks the other Resources tools in this session