Description
Summary CONFIDENTIAL PROJECT — This posting describes the role only. The full product specification, technical architecture, and proprietary concept are shared exclusively under a signed Non-Disclosure Agreement (NDA). Applying does not constitute access to the specification. Do not share or reproduce any information from this posting. What this project is The tool is a Gmail Chrome extension for sales and business professionals. It helps users organise and action the professional contacts and relationships in their inbox — providing tools for contact management, data quality, and outreach — all via official, user-authorised Google API access. API Compliance: All Gmail integration uses Google's official Gmail API and Chrome Identity API with explicit OAuth 2.0 user consent. The extension requests only the minimum scopes required for the user's own data. All functionality complies with the Google API Services User Data Policy, Chrome Web Store Developer Programme Policies, and Gmail permitted use guidelines. No email content is stored beyond the user's own session. This is a legitimate productivity tool, not an automation or scraping service. The planning and design work is complete. The product concept, specification, and all front-end components are fully documented. I need an experienced Chrome extension developer to build, integrate, and ship the product. The full 12-chapter product specification is provided on contract signature following NDA. It covers every feature, data model, API design, and UI component in detail. You are not expected to design or specify — only to build to the spec. What you're handed on day one The following deliverables are complete and shared immediately on NDA and contract signature: • Extension popup UI — fully coded 380px popup, all 5 tabs, ready to wire to a live backend • Gmail sidebar content script — sidebar injection and Gmail integration scaffold, ready to extend • manifest.json — MV3 manifest with all permissions declared • Node.js backend scaffold — auth, billing webhooks, and core API routes already structured • Landing page (v3) — fully coded homepage, ready to extend to multi-page site • Full product specification — 12-chapter document covering every feature, data model, and API • Brand assets — logo SVG, colour tokens, typography specification You are integrating and deploying fully specified, already-coded components — not starting from scratch and not designing the product. Confidentiality, NDA & IP Ownership This section is non-negotiable. All candidates must agree to these terms before receiving any product documentation. Non-Disclosure Agreement • A mutual NDA must be signed before the product specification or any proprietary materials are shared • The NDA covers: the product concept, technical architecture, codebase, user data model, and all business documentation • The NDA applies from the moment of shortlisting — not only on contract award • Shortlisted candidates who do not proceed to contract remain bound by the NDA • The tool's concept, feature set, and implementation approach must not be replicated, shared, or used in any competing project Intellectual Property • All code, scripts, documentation, and assets produced under this contract are the exclusive property of Daniel Thompson from the moment of creation • No contractor retains any licence, claim, or right to reproduce any part of the work product • Work product includes: source code, build outputs, tests, configuration files, and any derivative works Account & Infrastructure Ownership • All platform accounts must be created in, or transferred to, the name of Daniel Thompson or an agreed company entity • This includes: GitHub repository, Chrome Web Store developer account, Microsoft Edge Add-ons account, Supabase project, Stripe account, and any hosting/deployment accounts (Railway, Render, Vercel, Cloudflare, etc.) • No development or production account may be held in the contractor's personal name or on the contractor's personal billing • Credentials and access tokens must be transferred to Daniel Thompson at each milestone and immediately on contract termination • Contractor may be granted collaborator access during the engagement — this access is revoked on completion or termination Important: Any candidate who proceeds beyond shortlisting and receives the product specification, codebase, or any proprietary materials does so under the binding NDA. Breach of the NDA will be pursued through appropriate legal channels. Scope — 4 fixed-price milestones Phase 1 — Working prototype • Extension loads in Chrome Developer Mode, all 5 tabs functional, Gmail sidebar injecting correctly • Realistic mock data — no live backend required at this stage • Deliver: ZIP file + screen recording of complete walkthrough Phase 2 — Private beta (unlisted, invite-only) • Live backend connected: authentication, Gmail OAuth, core feature endpoints • Stripe billing integrated and tested end-to-end • Extension published to Chrome Web Store as unlisted — accessible only via direct private URL • Push update mechanism in place: extension can receive and apply updates without user action • Beta notification feature: in-extension notification system that can alert selected beta users when the public launch is ready, and prompt them to share with contacts • Beta tester access: a separate, non-expiring access tier for invited testers with grandfathered privileges (permanent free Growth plan equivalent) Phase 3 — Website live at agreed custom domain • Convert provided homepage to multi-page site: Home, Pricing, Features, Privacy, Terms • Deploy to agreed hosting on agreed custom domain • Lighthouse scores: Performance, Accessibility, and SEO all 90 or above Phase 4 — Public launch + handover • Switch Chrome Web Store listing from unlisted to public; optimise store listing • Trigger beta notification to all private beta users: in-extension prompt to share with contacts, activating viral loop • Submit to Microsoft Edge Add-ons (minimal rework from Chromium codebase) • Firefox port if MV3 compatible (optional — upper budget range) • Complete account handover: all credentials, env vars, and access transferred to Daniel Thompson • Full handover document: repository structure, deploy commands, environment variables, architecture overview Private beta — technical requirements The private beta is a critical phase. It must be built correctly from the start, not retrofitted. The following are hard technical requirements for Phase 2 delivery. Push Updates • Extension configured to auto-update from Chrome Web Store without requiring user action • Backend-driven feature flags to enable or disable functionality remotely per user or globally • Update cadence set to minimum CWS polling interval so fixes reach users within hours, not days Beta User Tier • A distinct Beta access tier implemented in the database and billing system • Beta users receive grandfathered permanent free access equivalent to the Growth plan — this tier never expires and is never overridden by standard billing logic • Beta users identified by email address via a seeded allowlist in the backend • Beta access is invitation-only: users receive a private install URL; extension is not discoverable on CWS during this phase Beta-to-Public Notification (Viral Loop Activation) • When public launch is triggered by Daniel, all active beta users receive an in-extension notification • Notification prompts beta users to invite colleagues, activating the viral loop at the moment of maximum product familiarity • Users who have previously used the tool have their contact list ready — inviting is a simple action • This notification must be built and tested during Phase 2, even though it fires at Phase 4 Skills required • Chrome Extension development (Manifest V3) — must have at least one published extension in the Chrome Web Store • JavaScript / TypeScript — React a plus; popup may use React + Webpack build pipeline • Gmail API + OAuth 2.0 — official integration using user-authorised OAuth 2.0 scopes (all access requires explicit user consent) • Supabase — auth, PostgreSQL, REST API (Firebase experience acceptable) • Stripe — Checkout + Billing Portal + subscription tier management • Node.js backend deployment — Railway, Render, or Fly.io • Static site deployment — Vercel / Netlify / Cloudflare Pages, custom domain setup How to apply Start your proposal with the phrase: "PROJECT VERIFY" — proposals without this phrase will not be considered. Then include all of the following: 8. Cover letter (max 150 words) — what makes you the right fit? Be specific. Generic copy-paste letters are declined. 9. Links to 1-3 published Chrome extensions — must be live in the Chrome Web Store (include extension IDs) 10. GitHub profile or portfolio — at least one TypeScript or JavaScript project visible 11. Answers to all three skills assessment questions (paste inline or attach as a document) 12. Confirmation you will sign an NDA — required before the product specification or any proprietary materials are shared 13. Your hourly rate — milestone prices are fixed; hourly rate applies to out-of-scope change requests only 14. Earliest start date — immediate preferred Shortlisting process: proposals reviewed within 48 hours. Shortlisted candidates will be asked to sign an NDA. The full product specification is shared after NDA signature. A 30-minute video call follows before any contract is issued. Questions about the role? Message me directly and I will respond same day.