A clear first step

What needs to happen
after “send”?

Choose one path. Check your starting point. Build a brief you can keep—or send for a scope review. No account, payment or test email.

The local brief tool needs JavaScript. You can still read the buyer’s guide or email support@teamveristria.com with your public app URL, chosen auth path and a short description. Do not include secrets.

01 / DEFINE YOUR PATH

Public app URL (required)

Public HTTPS URL only. No credentials, query parameters or auth links.

One auth-email path (required)

Who controls Auth settings? (required)

Does this path already exist in your app? (required)

Can you operate Supabase, sender and DNS settings? (required)

Is this a different kind of job? (optional)

What is the main job?

What do you want to happen? (required to send)

No passwords, API keys, tokens, live auth links or customer data. 20–1,500 characters if submitting a request.

02 / REQUEST A SCOPE REVIEW · OPTIONAL

Request a scope review

This sends your brief to Veristria’s intake. It does not book, charge you, configure your app or authorize test emails. We agree fit and scope first.

Your name (required to send)

Email for this request (required to send)

I agree to be contacted about this request and have read the privacy notice. This is not consent to unrelated marketing.

If intake is unavailable, keep the brief using copy or download. Nothing is sent automatically by email.

Local tool · no scan

A useful starting point.

Answer the questions and build your brief. This tool uses your answers only. It cannot inspect your private SMTP settings.

Your unsent brief will appear here.

Not generated. Not submitted.

$249 once, after scope agreement.

One sender and one existing auth-email path. Supplier costs separate. Missing app logic is a separate job. See the process.

What needs to happenafter “send”?

Request a scope review

What needs to happen
after “send”?