BUSINESS ASSEMBLY INTAKE

Start With the Outcome.

You do not need to know which tools, platforms, automations, or specialists belong in the system. Tell AMAL what you are trying to build, what exists now, and what the business can realistically support.

BEFORE YOU START

Give Us Enough to Underwrite the Situation. Not a Thesis.

The purpose of this intake is to reduce the interpretation burden on both sides. We need the objective, the economics you already know, the customer, the current operating setup, the available capabilities, and the constraints that could change the answer.

Do not submit passwords, bank or account numbers, credit-card information, API keys, Social Security numbers, tax IDs, authentication codes, or other credentials.

01 Contact & Business

Who are we evaluating, and what business are we looking at?

02 Business Snapshot

Give us the current operating picture before we discuss the target.

03 The Outcome

This is the center of the engagement. Start with what you want the business to produce—not the software you think you need.

04 Economics & Capacity

A strategy that the business cannot financially or operationally carry is not a useful strategy.

05 Current Operating System

Tell us what is already in the bag before we add another tool.

06 Constraints & What You Already Tried

We need to know where the system is actually resisting you.

07 Where You Think the Scope Belongs

You do not need to diagnose this correctly. This simply tells us what you believe you need.

Do not include passwords, bank/account numbers, card information, API keys, SSNs, tax IDs, authentication codes, or other credentials anywhere in this form.

Analysis Before Prescription.

Business Assembly is scoped around the operating burden of the actual situation. Software subscriptions, advertising spend, specialists, inventory, equipment, and other third-party costs are not assumed to be included unless a written scope specifically says they are.