This guide walks you through the platform end-to-end. Plan on about 25 minutes to work through every scenario. You can stop and pick back up later — the guide lives at /guide.
Vendorlogic is a B2B credit application platform for contractors (HVAC, plumbing, mechanical) and the vendors who supply them. The big problem we're solving: when a contractor applies for credit at a new vendor, the vendor's credit team has to chase 3–5 trade references by phone, fax, or email — and it takes days. Vendorlogic automates the whole loop.
The flow:
https://vendorlogic.vercel.app/. Bookmark it. The site is on Vercel + Supabase — no cold starts, fast page loads.Vendorlogic has three sides — Vendor (the credit team that issues credit), Applicant (the contractor applying for it), and Reference (the third party who confirms payment history). Plus an internal Platform Admin role for Vendorlogic operators.
When a vendor company signs up, the founder becomes the Org Admin automatically and can invite teammates with specific roles + per-user permission overrides:
view_pipeline but not decide_credit). The Org Admin can override any default per user — e.g. give one Sales Manager decide_credit for small-dollar applications. Toggle them on the Org Admin Users & roles page.Want to test as a credit manager AND a contractor AND a reference? You'd normally need three email addresses. Gmail has a hidden trick: every variant like you+vendor@gmail.com, you+contractor@gmail.com, you+ref1@gmail.com lands in your one inbox you@gmail.com. The platform sees them as different accounts.
So pick a base email and use plus-aliases for each role:
you+vendor@gmail.com — your Org Admin / Credit Manager accountyou+sales@gmail.com — invite this one as a Sales Manager lateryou+contractor@gmail.com — your applicant accountyou+ref1@gmail.com — a reference test addressTo watch both perspectives at the same time:
Work through these in order. Each scenario builds on the previous.
You're the first person at a fictional supply company joining Vendorlogic.
As Org Admin, invite another user to your org with a different role.
What happens when a second person from the same company tries to sign up — they don't get to barge in. They request access; the Org Admin approves.
Switch to the applicant side. We'll submit a one-time application as a contractor — no signup required.
Instead of typing every field on /apply, upload a PDF or photo of any credit application and AI fills in the form.
As credit manager, work an application end-to-end.
The Messages center has threads between vendor ↔ applicant ↔ reference. With two browser windows open, you can see messages appear live.
The third perspective — someone who got a reference request email.
As you test, jot down anything that surprises you. We're especially interested in:
These are deliberate beta cuts; we know about them.
Reply to whoever invited you to the beta with:
| What | Where |
|---|---|
| Sign in | /login |
| Create account / join org | /signup |
| Apply for credit (no signup) | /apply |
| Credit team pipeline | /dashboard |
| Application detail | /applications/[id] |
| Messages center | /messages |
| Org Admin · Users & roles | /admin/users |
| Contractor dashboard | /contractor/dashboard |
| Contractor messages | /contractor/messages |
| Reference inbox (signed in) | /reference-portal/inbox |
| Reference response (with email link) | /reference/[token] |
| Platform admin | /platform |
| This guide | /guide |
Thanks for testing. Tell us what you think. 🚀
Start at sign in