Journey
What must change?
Describe the failing customer or staff journey, current system, desired outcome, and why the issue matters now.
Direct intake / verified form
Send the smallest truthful map of the system.
Use the verified form, email, or phone so sensitive details stay out of a public page, and begin with the operating facts that determine whether the work is a fit.
People and language
Who uses and approves it?
List user groups, Hebrew/Arabic/English needs, directionality, accessibility expectations, content owner, and acceptance owner.
Data and vendors
What crosses the boundary?
Identify important data classes, identity, hosting, analytics, communications, AI, support, and other suppliers involved.
Transactions
How does value move?
Explain currencies, provider, settlement, invoices, refunds, reconciliation, and who owns commercial or professional decisions.
Continuity
What cannot simply stop?
State failure tolerance, manual fallback, support expectations, urgent contact path, rollback need, and operating constraints.
Timing
Which date is real?
Share the non-negotiable deadline, what drives it, who can make timely decisions, and what evidence must permit release.
Contact Logan directly
No portal. No automated promise.
Email a plain-language brief or call to discuss fit. Do not send passwords, private keys, payment data, health records, government identifiers, or other sensitive material in the first message.
A first conversation does not create an engagement. Work begins only after feasibility, screening, scope, responsibilities, payment, and written terms are agreed.