We’re The Sassenachs — Scottish elopement photographers and planners — building a lightweight “elopement OS” for tiny weddings. We’ve got a wireframe and clear scope. We need a pragmatic builder who ships, not a committee. What you’ll build (MVP) • Planner dashboard with Job, Timeline, Recommendations, Mood Board • Supplier magic links with scoped view, Confirm or Can’t make it, optional ETA • Timeline blasts by email or SMS with versioning and simple diffs • Recommendations library for accommodation, HMUA, celebrant, bagpiper, restaurants with reusable contacts • Plan A/B switcher that updates times and rebroadcasts in one click • Offline day-of PWA that caches the timeline, contacts and pins • Light docs/payments via integration first (Rock Paper Coin or Stripe links) • ICS attachments and Add to Apple or Google Calendar buttons Stack we have in mind • Next.js React with Tailwind • Node (Express or Nest) in TypeScript • PostgreSQL with Prisma • Email auth with magic links, simple roles and scoping • SendGrid or Postmark for email, Twilio for SMS • Vercel for frontend, Railway or Render or AWS for backend • Sentry for errors, basic tests, clear README Deliverables • Deployed MVP behind password with seed data • Git repo with sensible structure and instructions • Weekly check-ins with short Looms and a written changelog Nice to have • Maps with pins, parking notes and walk times • Timezone clarity during planning, local lock on the day • Hooks for e-sign later, basic analytics on supplier reliability How to pitch Send 2–3 relevant SaaS projects you shipped, a brief approach to the magic-link model and timeline versioning, a ballpark for a 6–8 week MVP, your availability. Start your message with Highlands so we know you actually read this. Must be comfortable working in UK English and building for a Scotland-based team.