Finish and launch a Supabase + Vercel staff web app (prototype built, 4 fixed milestones)

The goal Take our working prototype live. When you’re done, a real admin can add staff from inside the app, those staff can sign in on their phones and use it, and we’ve run a 2-week pilot with 5 people without issues. The core app is already built. This job is finishing the admin tools, setting up production, and supporting the pilot. We are not looking for a rebuild. What the app does It’s a mobile web app (PWA) for field crews at an oilfield services company. Staff add it to their phone’s home screen and use it like an app. Staff sign in with their email and a 6-digit code we email them. No passwords. Only emails an admin has added can sign in. After sign-in, they pick their division (there are 4) and see a grid of large tiles: SOPs, Forms, Training, Maintenance, and so on. Each tile opens an outside tool (Google Docs, Samsara, and others) or a list of links. Every tap is logged, so admins can see who opened which document and who hasn’t. Tech Supabase (Auth with email OTP, Postgres, RLS) and Vercel. Code is in a private GitHub repo with a written build plan. You’ll get access after we shortlist. Already built and working (demo mode, sample data) Email-code sign-in with access limited to approved emails Home-screen install and offline support Division picker, tile grid, tile pages Tap tracking Admin dashboard: activity feed and required-document tracking Staff list (view only; new logins are currently created by hand in the Supabase dashboard) What you’ll build Milestone 1: Staff management Admin can add a person (email, name, role, divisions) from the app, and that person can sign in immediately. Admin can edit a person’s divisions and admin status. Admin can change a person’s email (for example, personal to company email), and their activity history stays attached. Admin can remove a person, and their access ends immediately. All of this runs server-side. The service role key is never exposed to the browser. Done when: an admin can manage all staff without opening the Supabase dashboard. Milestone 2: Links editor Admin can add, rename, reorder, hide, and remove tiles per division. Admin can add, edit, and remove the links under each tile. Admin can edit the short login hint shown before a tool opens. Done when: an admin can change any tile or link without code or a redeploy. Milestone 3: Production launch Production Supabase project and Vercel deployment, set up under our accounts Custom domain connected Transactional email provider for login codes, with SPF and DKIM configured so codes don’t go to spam Sample data replaced with the real structure Short handover doc: how it’s deployed, environment variables, and how to make common changes Done when: the app runs live on our domain and codes arrive in Gmail and Outlook inboxes within a minute. Milestone 4: Pilot support Help us onboard about 5 staff on iPhone and Android Fix bugs found during a 2-week pilot Done when: the pilot group has used it for 2 weeks with no open bugs. What we provide Repo access, the build plan, the real tile and link content, the logo, account access for Supabase, Vercel, and the domain, and a quick response when you have questions. Who we’re looking for You’ve shipped production apps on Supabase (Auth, RLS, Edge Functions) and Vercel, and you’ve dealt with iPhone home-screen PWA quirks. You’re comfortable picking up someone else’s codebase. Budget and terms Fixed price, paid per milestone. Please quote each milestone separately and give an estimated timeline. All code and accounts stay under our ownership. To apply, answer these: How would you let an admin create a user from the app without exposing the service role key? Which email provider would you use for the login codes, and why? Describe one iPhone home-screen PWA issue you’ve run into and how you fixed it. Start your reply with the word “tiles” so we know you read the full post.