Short guide before the free consultation

What we actually do on the call

• We walk through what users see after important clicks (screen share or a clear written walkthrough).
• We compare what should happen vs what happens today (example: “after approval it should leave the queue, but it stays”).
• I explain in plain language where the issue likely sits—permissions, workflow steps, business rules, or product clarity.

What you get when we wrap

You do not get a 40-page audit PDF or a full quote on the spot.

• 2–3 notes written simply (no architecture jargon unless you want it).
• One or two actions you can try the next day (example: “write this rule in a doc”, “test with a single role only”).
• Or a clear “you do not need a big build yet”—that is still a useful outcome.

What to send first

One message is enough to start. It can include:

• What the product does in simple steps: “Employee submits a request → manager sees it in a list → approves or rejects.”
• Who uses it (roles), even internal names: “team lead”, “operator”, “admin”.
• What feels wrong: “it freezes at step 3”, “duplicates appear”, “a customer sees someone else’s data”.

Examples that save time

• More useful than “we want better UX”: “when X happens, user Y must not see field Z”.
• If you have a deadline or things you do not want, say it early—we skip irrelevant questions.

You do not need perfect prep

Screenshots, a rough sketch, or a short Loom-style description are all fine—often better than a long essay.