Limozly SaaS Platform Completion & Launch

Limozly is a multi-tenant B2B SaaS platform for limousine and black car operators. It is built, deployed, and substantially complete: seven portals, roughly 650 routes, a working booking and dispatch engine, CRM, pricing, settlements, and a public API.
We are looking for one experienced developer to take it from substantially complete to verified and launched. This is a finishing and hardening role, not a rebuild. Someone who enjoys greenfield architecture will be bored. Someone who takes satisfaction in closing the last fifteen percent properly will do well.
What you would be working on
Stack. Next.js 14 (App Router), TypeScript, Tailwind, Prisma, Supabase (Postgres, Auth, Storage), Stripe Connect, SendGrid, Twilio, Google Maps Platform, Vercel.
Domain. Each customer is a limousine operator running dispatch, bookings, fleet, drivers, corporate accounts, hotel partners, and operator-to-operator subcontracting. Multi-tenancy and correct financial handling are central to the product, not incidental.
Scale. Around 650 routes and roughly 160 data models. Mature, working, and consistent. Not a rescue.
Scope of the engagement
1. Verification and testing
Establish real test coverage where it matters most. The platform has been built rapidly and validated largely by inspection rather than by systematic testing. We need someone who will:
• test multi-tenant isolation properly, with real accounts across multiple companies
• verify permission enforcement across all seven portals
• exercise the pricing engine against known expected outputs
• test the payment paths end to end, including refunds, captures, and disputes
• validate the scheduled jobs and the notification pipeline
• set up whatever automated testing gives the best return, and say honestly what does not need it
2. Completion
A prioritized backlog exists and will be shared in full on engagement. It is a mixture of features that are built but not yet reachable from the interface, integration paths that need finishing, and a small number of genuine gaps. Most items are hours, not weeks.
3. Hardening
Security review and remediation before launch: credential rotation, tenant isolation verification, database access controls, audit logging completeness, and a review of the payment paths.
4. Launch
Take the platform to production readiness and through go-live. Includes release process, environment configuration, monitoring, and a rollback plan.
What we need from you
Required
• Senior-level Next.js App Router and TypeScript in production. Not tutorial familiarity: you should have opinions about server components, caching, and where things go wrong.
• Prisma and Postgres, including schema evolution on a live database without downtime or data loss.
• Stripe Connect specifically, not just Stripe. Destination charges, connected accounts, webhooks, and disputes.
• Real multi-tenant SaaS experience. You should already know why row-level security matters and what happens when application-level filtering is the only thing standing between two customers' data.
• A track record of taking something from nearly finished to actually shipped. This is the single most important line in this section.
Valued
• Transportation, logistics, dispatch, or marketplace software
• Supabase specifically
• Experience inheriting a codebase you did not write, and being honest about what you find
How you work
• You verify before you assume. This codebase has features that are built but invisible, and integrations that appear absent locally because credentials live only in production. Someone who concludes "this is missing" without checking will waste weeks.
• You are comfortable telling the founder that something is a bad idea.
• You can explain technical decisions to a non-developer without either condescending or hiding behind jargon.
How we work
This is a two-person build, not a handover. The founder is non-technical and directs development through written specifications, working alongside an AI coding assistant. That is how the platform reached its current state and it continues throughout the engagement. You are joining an active build, not inheriting an abandoned one.
Your role is senior engineering judgment, verification, and the decisions that need someone who reads code.
Practically this means:
• you own architecture, technical decisions, code review, and correctness
• the founder continues developing daily alongside you and is closely involved in every part of the product
• work is coordinated: you will be reviewing and building on changes made in parallel, and the founder will act on your direction
• anything you need verified by the founder must be doable in a browser or by running a command you provide
• written communication over meetings
If you would find it difficult to work alongside a non-technical founder who is actively writing specifications and shipping code, this is not the right engagement. If you would find it efficient, it is unusually so.
Existing conventions are documented in the repository and a full technical handover document exists. You will not be reverse-engineering from scratch.
Explicitly not in scope
• Rewriting the platform or migrating the stack
• Redesigning the interface
• Changing the payment architecture. Limozly deliberately takes zero percent of any ride. Operators are billed for software only, and ride money goes directly to their own Stripe accounts. This is a product decision and a competitive position, not an oversight.
• Building a native mobile application
Engagement shape
• Contract, remote, with a defined completion milestone rather than an open-ended retainer
• We would expect to start with a paid two-week assessment: you review the codebase, verify what works, and deliver your own prioritized plan with estimates. Both sides learn a great deal from this, and either can walk away cleanly at the end of it.
• After the assessment, a milestone-based agreement through to launch
• Rate and hours to be discussed. Tell us what you need to do this properly rather than what you think we want to hear.
Access and confidentiality
This is a live commercial platform with real operator data. Access is granted in stages, and only after both of the following:
1. A signed non-disclosure agreement. No repository, database, or infrastructure access is granted before this. No exceptions, including for evaluation purposes.
2. Verified experience. We check references and confirm the specific experience claimed, particularly around multi-tenant SaaS and Stripe Connect. We will ask to speak to someone who worked with you on a comparable system.
Once both are complete, access is provisioned for the assessment period, scoped to what the work requires. Full production and infrastructure access follows the assessment, not before it.
We are direct about this because a previous engagement ended, and revoking access across a dozen systems taught us to grant it deliberately in the first place. We expect any senior candidate to consider this normal, and we extend the same seriousness to your interests: the agreement will be mutual and reviewable before signature.
To apply
Please send:
1. Two or three examples of production systems you have shipped, ideally multi-tenant SaaS. Links or a short description of your specific role.
2. Your experience with Stripe Connect, described concretely.
3. A short answer to this: you join a project where a feature appears to be missing. Before concluding it needs building, what do you check, and in what order?
4. Your availability and rate.
5. Two references we may contact, at least one from a project comparable in scale or domain.
We will not ask you to complete an unpaid take-home exercise. The paid assessment is the evaluation, and it begins once the NDA is signed and references are confirmed.