Atlas tool / project canvas No sensitive data
MA Faith Forge Labs Morocco systems atlas Open project canvas
Atlas / Project canvas

Prepare before contact

Describe the operation—not the imagined app.

A useful first conversation about a project serving Morocco needs the problem, people, handoffs, current systems, constraints, and desired result. It does not need passwords, private records, a finished specification, or invented certainty.

Seven canvas blocks

Write one or two paragraphs for each.

Keep the first brief at a business level. Sensitive data and system access belong in an agreed secure process after both sides decide to proceed.

1. Operating problem

What repeatedly goes wrong, takes too long, stays invisible, or prevents the organization from offering something important?

2. People and roles

Who requests, approves, performs, reviews, supports, and owns the work? Include external users and partners.

3. Current route

Describe the steps today, including email, spreadsheets, paper, messaging, websites, business software, and manual re-entry.

4. Systems and vendors

Name products that may need to stay or connect. Say who controls the accounts and whether documentation or API access is known.

5. Data and language

Describe information categories—not actual records—and whether the experience needs English, French, Arabic, mixed script, or right-to-left behavior.

6. Transactions

If money or orders are involved, identify currencies, providers, settlement, fulfilment, refunds, records, and the people who own those decisions.

7. Success and constraints

State the measurable result, timing pressure, budget boundary, required continuity, and anything the project must not disrupt.

Safe first contact

What not to send.

Do not include passwords, private keys, payment-card details, bank information, identity documents, medical information, customer lists, production exports, or other confidential records in an initial email. Describe the category and consequence instead. If deeper review is appropriate, access and information handling can be agreed first.

What happens next

  1. Faith Forge Labs reviews whether the problem appears to fit remote technical discovery.
  2. A conversation clarifies the operating result, decision owners, current systems, and major boundaries.
  3. If appropriate, the next step is documented. It may be a discovery engagement, a narrow technical review, or a conclusion that another route fits better.
  4. No build, price, schedule, compliance conclusion, or provider eligibility is assumed until the relevant facts are available.

Send the prepared canvas

Use direct contact when the seven blocks are ready.

Lead with the organization, the operating problem, and the intended users. Keep confidential details out of the first message.

Call 404-939-0637 Email the project canvas

Faith Forge Labs is based in the United States and works remotely.