Outcome and audience
Describe one complete user task, who performs it in or around Jordan, current pain, device context, support path, and evidence of success.
Project packet / no automated promise
Bring the decisions that make a responsible Jordan estimate possible.
There is no intake form that converts a country name into a quote. Assemble the packet below, mark unknowns honestly, and contact Faith Forge Labs directly for a scoped technical conversation.
Working checkpoints
A useful packet describes the real operating system.
Screenshots, sample records, current URLs, workflow notes, provider documentation, and named owners are more useful than a long wishlist without context.Language and content
State the English and Arabic scope, final content owner, Arabic reviewer when needed, RTL acceptance responsibility, and any existing approved material.
Data and systems
List necessary data, current systems, source of truth, integrations, vendors, locations, access owners, retention expectations, and known risks.
Transaction and release
Describe offer, currency, payment/provider path, receipt or invoice handoff, fulfillment, refunds, reconciliation, release authority, and rollback needs.
Route
Work through the packet before requesting dates.
- 01
Collect evidence
Provide existing source or access, screenshots, sample data with sensitive material removed, failure examples, analytics context, and provider references.
- 02
Name decision owners
Assign business, technical, language, data, payment, tax, content, specialist, acceptance, release, incident, and support owners.
- 03
Separate unknowns
Mark what needs research, vendor confirmation, local professional review, technical discovery, recovery, or a product decision.
- 04
Define done
List the devices, routes, languages, workflows, failures, reports, accessibility checks, production proof, documentation, and handoff required for acceptance.
Contact is direct, not automated.