Prove it in three weeks, then build the whole platform
Your spec, product plan and Figma designs are already done — you need a team that can execute them with light oversight, not heavy management. Exactly as we discussed: start with a fixed-price trial milestone on the OTP and authentication flow, then move to the full multi-phase build once we've both seen how we work together.
What we heard on our call
- This is greenfield, and already specced. Full technical spec, product spec and high-fidelity Figma designs are done by your team — you need execution, not supervision.
- Light oversight, not day-to-day management. Async updates, a video call each week (twice a week for the first two weeks), and visibility into the board.
- Your process is already set: NDA → redacted developer CVs → technical interview → a paid, fixed-price 2–3 week trial on the OTP/auth flow with 2–3 devs → a go/no-go call → a multi-year, multi-phase engagement with AI features and maintenance down the line.
- You and your fractional VP of Product are our direct contacts — not a layered account-manager setup — and the LendIQ owner stays out of day-to-day.
- Open to fixed-price or hourly. You mentioned a blended range around $45–60/hr for senior full-stack work if we go hourly.
- AI-assisted development is welcome — enterprise accounts only, no training on your data, every PR human-reviewed, with extra peer review on security- and RLS-sensitive backend code.
- No rush. You expect to decide in the next couple of weeks.
The path you outlined
We're following the process exactly as you laid it out on the call.
- Sign the NDA
- Send over the detailed requirements doc
- We send redacted CVs for the Lead, Frontend and Backend devs
- Short technical interview with the named team on an Upwork call
- 2–3 week fixed-price trial: OTP + authentication, built on your RLS/multi-tenant spec
- Go/no-go call once the trial is delivered
- Phase 1 of the full build, priced once we've reviewed your spec in detail
- Phase 2+: AI features, ongoing maintenance, multi-year roadmap
Your trial team
Named developers on the technical interview, the weekly calls and the trial commits — not account managers.
Owns the RLS/multi-tenant design under connection pooling and the auth architecture.
Builds the OTP and auth services, Supabase setup and the security-sensitive data layer.
Implements the auth UI against your Figma designs and wires it to the backend.
What's included
- Direct Slack access to you and your product owner — no layered account management.
- Asana board visibility into every task the team is working on, updated as work moves.
- Weekly video call (twice a week for the first two weeks), plus async written updates in between.
- GitHub repo access once your Supabase backend and prod/test branches are set up.
- AI-assisted development on enterprise accounts only, with mandatory human review on every PR and peer review on RLS- and security-sensitive code.
- Everhour time tracking ready for any hourly work later, fully compliant with Upwork's policy on agency-side logging.
What we checked before quoting
We ran the technical questions your spec raises against what's actually standard before putting a number on the trial.
RLS under connection pooling
Under transaction-mode pooling (Supavisor, PgBouncer), a plain session-level tenant id isn't safe — it can leak between requests. We'll use SET LOCAL / set_config scoped per transaction from the start, or recommend session-mode pooling if your expected concurrency allows it.
Upload quarantine-to-clean pipeline
Standard pattern once we know the provider (e.g. S3/GCS with a scanning step between a quarantine and a clean bucket) — we'll confirm this as part of the trial kickoff.
Background workers, migrations & outbox retries
Tenant-scoped background jobs, backward-compatible SQL migrations (expand/contract) and idempotent outbox/webhook retries are all well-understood patterns — no platform limitation.
Immutable money-movement history
An append-only ledger table, with corrections made as new offsetting entries rather than updates or deletes — the normal approach for financial ledgers.
Trial milestone and pricing
This is our estimate for the 2–3 week OTP/auth trial you described, built from the blended $45–60/hr range discussed and a 3-person team. As you said on the call, it converts to a fixed price once team selection and scope review are final — we'll confirm the real number as soon as we've reviewed your requirements doc.
Kickoff & environment setup
- Supabase, GitHub (prod/test branches), Asana and Slack set up
- RLS-under-pooling approach confirmed and documented
OTP & auth backend
- Authentication service, OTP flow, tenant-scoped RLS policies
- Peer-reviewed security pass on sensitive code
Frontend integration
- Auth UI built to your Figma designs
- End-to-end wiring against the backend
QA & go/no-go handoff
- Full QA pass and staging deploy
- Walkthrough on our weekly call for your go/no-go decision
Ad hoc or out-of-trial-scope work is billed at $40/hr through Everhour. If you'd rather run the whole engagement hourly instead of fixed-price, we're glad to — same blended rates, same reporting.
After the trial
Exactly the path you described: a go/no-go call, then the full platform.
| Stage | What happens | Pricing |
|---|---|---|
| Go/no-go call | Review the trial milestone together and decide whether to continue | — |
| Phase 1 build-out | Full greenfield build against your spec and Figma designs | Fixed-price milestones, quoted after requirements review |
| Phase 2+ | AI features and later phases, as you scope them | Quoted per phase |
| Ongoing maintenance | Ongoing support once you're live | Fixed monthly or $40/hr, your choice |
When is it done?
What we need from you
- Signed NDA so we can share CVs and go deeper on specifics.
- The detailed requirements document you mentioned, so we can finalize the trial scope and team.
- Your expected transaction/active-user volume — it decides whether transaction-mode or session-mode pooling fits better.
- Supabase project access once it's set up, plus a GitHub org we can be added to.
- The weekly (twice-weekly at first) video call and Slack access to you and your product owner.
Relevant work
alter.software ↗
Mentioned on our call as adjacent SaaS work from our team.
raiseforward.org ↗
A Stripe-based fundraising platform with dashboards and financial reconciliation — the closest parallel to LendIQ's money-movement needs.
driveroadside.com ↗
Mentioned on our call as adjacent SaaS work from our team.
How we work
- In-house, not outsourced. We're a ~70-person team, mostly based in Pakistan, on our payroll — a true agency model, not freelancers pulled together per project.
- 12 years in business, 8 on Upwork. We've worked across industries, including SaaS and financial-reconciliation platforms like RaiseForward.
- Named developers, not account managers. The people on your technical interview and weekly calls are the people writing the code.
- AI used responsibly. Enterprise accounts only, no training on your data, every PR human-reviewed, extra peer review on anything security- or RLS-sensitive.
- Upwork-compliant tracking. Everhour for any hourly work, since not all 70 of us hold individual Upwork profiles — fully within Upwork's agency policy.
Next steps
- Sign and return the NDA.
- Send over the detailed requirements document so we can finalize the trial team and scope.
- Review the redacted CVs and join a short technical interview call.
- Kick off the fixed-price OTP/auth trial milestone.