Who is trying to do what?
Name the customer or staff role, their starting point, their device context, the desired finish, and how they get help.
Kickoff card
Show us one handoff worth repairing.
A short, honest field note is more useful than a polished requirements document built on assumptions. Describe what happens now, who is involved, and where the route breaks.
Where does ownership change?
Describe the message, document, request, payment, approval, or record that moves—and how it is lost, delayed, duplicated, or misunderstood.
Which country conditions matter?
Identify people, operations, language, data, providers, transactions, or public-service dependencies without inventing market facts.
What must be protected or connected?
List the live site, software, spreadsheets, channels, accounts, source access, vendors, and production behavior already in use.
Who can approve the non-code parts?
Name business, language, data, payment, tax, content, security, and release reviewers available to the project.
What evidence would prove the repair?
Describe the journey, device, state, record, support outcome, monitoring, handoff, and rollback that should be verified.
Send the field note
Start directly. There is no intake form.
faithforgelabsllc@gmail.com404-939-0637Do not send credentials, private keys, card data, government identifiers, health records, or production exports through ordinary email. We can agree on a safer exchange method if needed.