Your Role: You will serve as the final authority on my financial health. This is a high-level advisory role. You are not a daily bookkeeper; you are the architect who sets the "rules of the road" for my bookkeeping team, audits their execution quarterly, vets potential acquisitions, and takes full responsibility for my annual tax filings. Mandatory Requirements: Credentials: Must be a licensed CPA in the United States. M&A/Vetting Expertise: Proven experience in analyzing small-to-mid-sized business acquisitions (due diligence, deal structure, and financial health assessment). Strategic Advisory: Deep expertise in tax strategy, entity structuring, and multi-state compliance. Equity Fluency: Demonstrated ability to interpret, account for, and structure equity agreements and capital stacks. Communication: Proactive, crisp, and accessible. You must be available for occasional ad-hoc advisory calls/emails between our formal quarterly review cycles. Key Responsibilities: Strategic Blueprinting: Develop the technical accounting guidelines (equity treatment, intercompany flows, state nexus) for my bookkeeping team to execute daily. Deal Vetting: Act as a "third pair of eyes" on potential acquisitions, providing objective financial analysis to determine if a deal is a "buy" or "pass." Quarterly Oversight: Conduct deep-dive reviews of my portfolio to ensure audit readiness and strategic alignment. Tax Strategy & Filing: Design a forward-looking tax plan and manage all annual federal and state filings for the enterprise. On-Demand Advisory: Serve as an ongoing resource for financial questions, risk management, and tactical decision-making. The Ideal Candidate: You are a business-minded advisor, not just a tax preparer. You understand how to spot "red flags" in a P&L, you know how to structure an equity deal to protect all parties, and you communicate with the clarity required for a fast-moving, one-person operation. You view yourself as an extension of my business leadership team. How to Apply: Please provide: Proof of current CPA licensure and standing. A brief summary of your experience in due diligence for business acquisitions. An example of your process for vetting a potential business deal—what are the first three things you look for? Confirmation that you are comfortable with a quarterly review model supplemented by periodic advisory access.

Engagement Overview I am the CEO and principal attorney of a small law practice specializing in campaign finance, lobbying regulation, FARA, nonprofit law, and government ethics. My five-person team — a junior partner, two associates, and an executive assistant — recently integrated into a larger firm. I am looking for an experienced Claude/AI automation builder for a phased engagement to design, build, and deploy a suite of interconnected agents and automations. This brief covers three phases. Phase I (Inbox Triage) is the highest immediate priority and the natural starting point. Phases II and III follow sequentially. Strong candidates will be evaluated on Phase I but should demonstrate familiarity with the full roadmap. This is a paid engagement. Scope, timeline, and rate are open to discussion. Technology Stack Email: Gmail (personal Pro account — not firm infrastructure) AI: Claude (Anthropic) via MCP or API Task and project management: Notion (existing workspace; routing tables, matter tracking, and timesheet structure already in place) Calendar: Google Calendar Internal chat: Google Chat Document storage: Google Drive (primary); local hard drives on iMac and MacBook Pro (secondary) Matter management / DMS: iManage (larger firm system — integration via dedicated ingestion email address) Voice notes: Plaud (AI note-taker) Signing platform: TBD — candidates should ask during scoping Out of scope: Signal and iMessage — encrypted platforms with no API access; manual forwarding convention only Confidentiality Requirements This is a law practice. Attorney-client privilege and work product protection apply to all client communications and matter-related documents. These are not compliance checkboxes — they are professional obligations with real consequences. The successful candidate must: • Execute a non-disclosure agreement prior to engagement • Demonstrate genuine understanding of why data handling matters in a legal context — not just technically, but professionally • Never use client names, email content, routing data, or document content for training, testing, or demonstration purposes • Work exclusively within the client's authenticated accounts — no third-party data stores outside the approved stack • Design systems that minimize data exposure — process and route, do not store unnecessarily Generic proposals that do not address confidentiality specifically will not be considered.   Phase I — Inbox Triage Agent Real-time classification and routing of inbound Gmail, with a daily digest to the executive assistant. Objective The principal attorney's Gmail inbox receives high volumes of email across clients, matters, and categories of widely varying priority. The goal is an agent that processes every inbound message, classifies it, routes it to the correct person automatically, and ensures nothing drops — without overloading the executive assistant with triage work she should not be doing. Two-Stage Routing Logic Stage 1 — Sender Classification Every inbound email is classified against a tiered contact list maintained in a Notion database: MVC: Most Valuable Clients — 5 to 10 contacts. Highest priority. HVP: High Value People — 10 to 20 contacts. Some overlap with MVCs. Principal attorney, unless task-type rule applies All other clients: Roster managed in Notion with assigned attorney(s). Assigned attorney(s) per Notion client record Catch-All: Anyone not in the contact table — prospects, opposing counsel, vendors, bar association, etc. Generate executive assistant daily digest Stage 2 — Task-Type Classification (MVCs only) For MVC contacts, a second classification layer routes based on the nature of the request. Rules are client-specific. Examples: • Scheduling requests → Executive assistant • Contracts and approvals → Designated associate(s) per client record • Strategic and substantive legal matters → Principal attorney Task-type rules are defined per MVC client and must be configurable without developer involvement. Routing Table — Notion All contact and routing data lives in an existing Notion database. The agent reads from it at runtime. Required fields: • Contact name and/or email domain • Tier (MVC / HVP / Standard / Catch-All) • Assigned attorney(s) for Standard clients • Task-type override rules for MVCs The executive assistant must be able to add, edit, and re-tier contacts without touching code. This is a hard requirement. Routing Output Candidates should propose their recommended approach from among the following, based on current Gmail MCP capabilities: • Apply Gmail label and/or forward to assigned attorney's address • Create a pre-addressed draft for principal attorney review before sending • Log routing decision to Notion with email link and recommended assignee Please address this question directly in your proposal — it is a key evaluation criterion. Daily Executive Assistant Digest Once per day at a configurable time, the agent generates a digest delivered to a designated Notion page covering all catch-all emails from the prior 24 hours. Each entry includes: sender, subject, timestamp, and a one-line AI summary of the email's apparent purpose.   Phase II — 5 AM Daily Brief A structured morning brief delivered to Notion each day before 5 AM, aggregating schedule, tasks, workflow status, news, and forward-looking context. Objective The principal attorney starts each day across multiple locations and needs a single, consolidated view of what matters — professional and personal — without opening email. The brief is delivered to a dedicated Notion page and covers the sections below in the following order. Section 1 — Daily Schedule Full calendar for the day pulled from Google Calendar. All events, calls, and commitments in chronological order. Section 2 — Open Projects and Undone Tasks Two sub-sections: (a) MVC high-value work — open projects and incomplete tasks for Most Valuable Clients, filtered to substantive legal work only; and (b) Personal — all open personal projects and tasks without exception. Personal items are comprehensive by design: if it is not surfaced here, it will be forgotten. Source: Notion task and project database. Section 3 — Blocking What is the principal attorney specifically holding up? Items where others in the firm are waiting for a review, decision, approval, or action. Source: Notion matter and task records where assignee or status indicates the ball is in the principal attorney's court. Note to builder: this section requires careful logic design. The agent must infer from status fields and assignee data what is genuinely waiting on the principal attorney versus what is simply unresolved. Work with client during onboarding to define the exact field logic. Section 4 — News Digest Industry News Curated digest of overnight developments in: campaign finance law and FEC activity, election administration, lobbying regulation (federal and state), nonprofit political activity, and government ethics. Format: short summary of each item with a link to the full article. Aim for signal, not volume — 5 to 10 items maximum. US Political News 5 to 10 headlines with links covering: presidential politics, US Senate and House elections, and major gubernatorial races. Stories people are actually talking about, not wire service filler. Section 5 — Firm Workflow Matter-level status summary pulled from Notion, organized by client tier and activity: Status Definition Closed Completed yesterday Moving Action taken yesterday Paused No action yesterday Stuck No action in five or more days Client groupings: MVCs (non-high-value work), Standard clients (all work), and any other open matters. Section 6 — One Month Look Ahead Rolling 30-day forward view pulled from Google Calendar covering: regulatory filing dates and compliance deadlines, matter-level deadlines, client birthdays, holidays, and planned vacations or travel. Anything that requires preparation or awareness in the next 30 days. Section 7 — Personal Financial Summary (If Feasible) Summary of personal financial position pulled from Monarch Money, if an API or MCP connector is available. Candidates should investigate Monarch's API access and address feasibility in their proposal. If not currently feasible, this section is omitted without affecting the rest of the brief. Delivery Notion only — not email. A dedicated page refreshed each morning before 5 AM. Previous day's brief should be archived, not overwritten.   Phase III — Night Maintenance Three nightly agents that run after close of business: timesheet creation, document filing preparation, and Plaud note routing. All outputs are delivered to Notion for principal attorney review. Part 1 — Timesheet Creation Objective Each evening, the agent reviews the day's activity across three sources and populates a timesheet in an existing Notion template for the principal attorney's review and finalization. Sources • Google Calendar — all events and calls attended • Gmail sent items — emails sent that day, grouped by client/matter where inferable • Google Chat — internal messages sent, grouped by thread/matter where inferable Note to builder: Google Chat API access will need to be confirmed alongside Gmail and Calendar MCPs. Confirm availability and any OAuth scope requirements in your proposal. Output: Populated Notion timesheet using existing template structure. Principal attorney reviews each morning, adjusts entries as needed, and finalizes. The agent does not finalize — it drafts. Part 2 — Document Filing Objective Each evening, the agent surfaces documents created or edited that day for the principal attorney's review. The attorney flags finals, and the agent forwards them to the firm's iManage ingestion email address for filing. Sources • Google Drive — documents created or modified that day • Local hard drives — iMac and MacBook Pro Note to builder: local hard drive access requires a locally-running component (daemon, Claude Code instance, or folder-watching script) on each machine. Please address your proposed approach to this in your proposal. Alternative approach for consideration: a designated 'Ready to File' folder on each machine that syncs to Google Drive. The attorney drags filing-ready documents into this folder throughout the day; the agent watches the folder and processes from there. Simpler architecture, device-agnostic, and builds a consistent filing habit. Candidates should evaluate and recommend. Output: A Notion page listing all documents surfaced for that day, with document name, location, and last-modified time. Principal attorney marks finals. Agent forwards marked documents to the iManage ingestion email address. iManage filing is handled by firm IT from that point — no direct iManage API integration required. Part 3 — Plaud Note Routing and Archiving Objective: The principal attorney uses a Plaud AI note-taker on calls and meetings. Each evening, the agent pulls new Plaud summaries, routes them to the appropriate team members, archives a copy to Notion tagged to the relevant client matter, and deletes the underlying audio and transcript from Plaud's platform and the local device. Prerequisite — Plaud API Plaud API or webhook access is a prerequisite for this part. Candidates must investigate and confirm availability before scoping. If Plaud does not currently support programmatic access, this part will require a manual export step as a workaround — please address both scenarios in your proposal. Routing Logic: Similar in structure to Phase I inbox triage routing (MVC/HVP/Standard tiers with task-type overrides) but with distinct rules to be defined with the client during onboarding. Do not assume inbox triage rules apply directly. Archiving: One copy of each Plaud summary is saved to Notion as a note, tagged to the relevant client matter. Tagging logic to be defined during onboarding. Deletion: After successful routing and archiving, the agent deletes: (a) the audio and transcript from Plaud's platform via API, and (b) any local copies on the principal attorney's devices. Local deletion requires the same locally-running component described in Part 2. Candidates may propose a unified local agent that handles both Part 2 and Part 3 local operations.   What I'm Looking For Strong candidates will have: • Demonstrated experience building Claude-based automations or agents — not general AI experience • Hands-on experience with Gmail MCP, Google Calendar MCP, and Notion MCP (or equivalent API integrations) • Ability to build systems that non-technical users can maintain — editability and simplicity are as important as technical sophistication • Comfort with phased delivery — Phase I first, Phases II and III following sequentially based on performance • Experience with professional services clients (legal, financial, consulting) is a meaningful plus • Willingness to execute an NDA and work within a legally sensitive environment What to Include in Your Proposal Please address the following specifically. Proposals that do not engage with these questions will not be considered. • Your proposed technical architecture for Phase I — how you would connect Gmail, Claude, and Notion • Your answer to the Gmail MCP routing output question in Phase I (labeling vs. drafts vs. Notion logging) — what is actually supported and what do you recommend • Your assessment of Plaud API availability and your proposed approach for Phase III Part 3 • Your assessment of Monarch Money API feasibility for the Phase II financial summary section • Your proposed approach to local hard drive access for Phase III Parts 2 and 3 — daemon, sync folder, or other • A comparable project you have delivered — describe the client type, the stack, and what made it work • Your estimated timeline and rate for Phase I, and a rough order-of-magnitude estimate for Phases II and III • Confirmation that you are willing to execute an NDA prior to engagement I am looking for someone who has read this brief carefully and has a specific, informed point of view on how to build it. This is phase one of a longer automation roadmap and the right candidate will be a long-term partner, not a one-time contractor.

Overview Transit & Flow is a fast-scaling Columbus home services company (plumbing, HVAC, drain, sewer, water heater, sump pump) building a premium, AI-powered operation. We are wiring together a set of best-in-class platforms into one self-functioning system that captures, books, reschedules, reminds, invoices, and follows up with customers automatically across phone, website chat, and Thumbtack. We need a senior integration specialist to stand this up cleanly, end to end, on a short-term contract. This is an execution role for someone who has built production voice-AI and automation systems before, not a learner. Detailed architecture blueprints will be provided to the hired contractor under NDA. What you will build A connected stack with no manual re-entry between systems: • Bland AI voice agents (several agents: inbound scheduler, after-hours and emergency handling, Thumbtack lead agent, and an outbound reminders and follow-up agent) • A website chat agent running the same booking logic in text • Thumbtack Live Connect bridged to a Bland agent via API and webhook, plus the Thumbtack lead feed into our automation bus • Quo.com as the telephony and SMS layer (call forwarding to Bland, SMS send via API, one consistent business number) • GoHighLevel CRM integration (contact sync, pipelines, nurture) • Make.com as the orchestration layer (scenarios for booking, rescheduling, reminders, estimates, invoicing, lead intake, error handling) • Scheduling, rescheduling, cancellation, and automated appointment reminders against our field service management platform (currently Jobber, migrating to OctopusPro, so platform-flexible API work is required) • Email automation including emailing and resending invoices and receipts on request Core responsibilities • Configure Bland pathways, custom tools, and webhooks that read and write to our systems mid-call (check availability, book, reschedule, cancel) • Build robust Make.com scenarios with idempotency, retries, error handling, and alerting • Integrate REST APIs and webhooks across Bland, Quo, GoHighLevel, Thumbtack, the FSM, and email • Bridge Thumbtack Live Connect to a dedicated Bland number so leads are answered live • Implement automated SMS and voice reminders with confirm and reschedule handling • Document everything and deliver a clean handoff so the system is maintainable and scalable Must-have skills • Proven production experience with a voice-AI platform: Bland strongly preferred, or Vapi, Retell, or Synthflow with transferable skill • Advanced Make.com (or n8n) including webhooks, data stores, error handling, and routing • Strong REST API and webhook integration skills, JSON, authentication, signing • GoHighLevel API experience • Telephony and SMS concepts: call forwarding, SIP or number routing, A2P • Ability to design for scale and reliability, not just a demo that works once Nice to have • Quo.com or comparable VoIP platform experience • Thumbtack pro tooling or lead-response automation experience • Home services or field service management background • OctopusPro, Jobber, or similar FSM API experience Engagement • Short-term contract, estimated 3 to 5 weeks • Milestone-based fixed price preferred, hourly considered for the right expert • Async daily updates, a few live working sessions per week • NDA and scoped system access required; you will not receive owner credentials How to apply Do not send a generic proposal. Answer these in your application: 1. Link or describe a voice-AI agent you built that booked or scheduled against a live external API mid-call. What platform, what API, what was the hardest part? 2. How do you make Make.com or n8n scenarios idempotent and resilient to duplicate webhooks and failed calls? 3. In two or three sentences, how would you bridge Thumbtack Live Connect to a voice AI agent so the agent answers the lead live? 4. Your proposed milestone breakdown and realistic timeline for the scope above. 5. How you handle client credentials and secrets securely. Strong applications that show real systems thinking move to a short paid test task before the full award.

We are interested in developing a web app that will allow us to automate a lot of the administrative tasks we need to do to carry out our work. The app will serve three main functions: 1) Provide a simple and easily accessible interface that will allow users to submit expense information that will be automatically stored in our organization's Google Drive. 2) Allow for admin to review this information and engage in a dialogue with the user if necessary. 3) Track all expense data in an organized way to a) allow users to view project expense summaries and b) allow admin to create and generate expense reports. Attached is an overview of how each interface should articulate with the others as well as a detailed summary of what each interface could look like. Note that the details here are not comprehensive and questions are expected, but the general shape is there. Note that these interfaces will need to effectively and seamlessly articulate with one another as well as external systems like Quickbooks.

Developer Scope of Work Project Overview & Engagement Terms Domexa Labs for MyCondoCompliance (mycondocompliance.com). MyCondoCompliance is an enterprise and consumer-facing web platform built to aggregate, OCR, analyze, and report on condominium association compliance data throughout Florida (starting with Miami-Dade County). 1. Key Engagement Expectations: Dedicated Weekly Support: We require reliable, continuous development capacity week-over-week to support platform growth, new features, maintenance, and internal system updates. Flexible Monthly Hours: Hours will flex on a month-to-month basis depending on business priorities, product release cycles, and current backlogs. Minimum 2-3 hours/week, not to exceed 15hrs/week. Rapid Turnaround & Steady Communication: We operate in a fast-paced environment. Quick turnarounds on hotfixes, active updates on tasks, and daily/structured communication are critical. Language Requirement: Excellent, professional verbal and written English is a strict requirement for technical syncs, documentation, and coordination. 2. Technical Infrastructure & DevOps Architecture The MVP is complete, live, and deployed. You will inherit the following technical ecosystem: Infrastructure Stack: - Code Repository: Managed via GitHub. - Front-end Hosting: Deployed and managed on Netlify. - CI/CD: Automatically triggers deployment to production on master branch updates, and to staging/dev on dev branch updates. - Back-end Hosting & Infrastructure: Managed on Digital Ocean inside a Kubernetes environment. - DNS Administration: Managed on Digital Ocean. - Third-Party API Integrations: - Mapbox: Powers map-based search and property discovery. - Mailgun: Handles transactional email delivery. - Chatbase: Integrated for natural language querying and chat functionality. - TipTap: Rich text editor powering board notes and internal editing. 3. Scope Evolution & Core Pipelines As our incoming developer, you will be expected to maintain, debug, and expand upon the core features built during our initial execution phases. A. Data Pipelines & OCR Ingestion Engine - Website Scraper/ETL: Continuous ingestion pipelines that pull structured condo data and metadata from county public registers. - Normalization Engine: Ingestion pipeline that categorizes incoming unstructured documents into strict schemas - OCR & Vectorization: All ingested documents are automatically processed via an OCR layer, and the resulting plaintext is indexed into a vector database for semantic search and Retrieval-Augmented Generation (RAG). B. Autonomous AI Processing Agents We run specialized Python/Node microservices to process aggregated document metadata: - Granular Extraction: AI agents systematically query vector databases to extract critical datapoints - Audit Trails & Provenance: Each extracted datapoint must carry verification properties—linking back directly to the document source, specific page/snippet, and extraction timestamp. C. Portal Tiering & Client Features - Consumer Interface: Detailed property pages, dynamic scoring components, PDF report compilation and downloads. - Enterprise Interface: Multi-tenant web app allowing real estate, financial, and legal clients to access deep search, structured list filtering (e.g., filtering condos by unit counts, reserve posture, specific clauses such as "Kauffman language", and termination criteria), and batch export controls. - Admin Dashboard: Tracks user engagement metrics, domain lookups, purchase histories, and mailing list extractions.

Deploy an existing Node.js/Express app and configure SMS. I have a complete, working dispatching app (Node + Express + SQLite, plain-JS frontend). I need someone to: (1) deploy it to Render or Railway with a persistent disk and HTTPS, (2) set up a Twilio account/number and wire in the credentials so it sends automated daily texts, (3) confirm the 6 AM scheduled texts fire reliably, and (4) be available for small tweaks afterward. Code, README, and deploy steps are all included. Should be a few hours for someone experienced. Please share similar Node deployment work you've done.

Project Overview We are seeking an experienced React developer to complete and enhance an existing web-based title and real estate document management application. The software is approximately 80% complete and is currently deployed and operational. The application is used to manage title search orders, enter title data, track chain of title information, and generate real estate-related documents. We are looking for a developer who can review the existing codebase, understand the current architecture, and complete the remaining development tasks. Current Technology - Existing React-based web application - Source code maintained in GitHub - AWS-hosted deployment - Existing database and user interface already functioning Scope of Work 1. User Interface Enhancements - Add new data entry fields throughout the application - Modify existing forms and layouts - Improve usability and workflow efficiency - Ensure data validation and proper field formatting 2. Title Data Management - Enhance title search and chain-of-title data entry screens - Support additional title-related information fields - Maintain automatic organization and sorting of title records 3. Dynamic Document Assembly - Complete the document generation system - Generate Microsoft Word documents from entered data - Populate templates with user-entered information - Conditionally include or exclude sections based on available data - Support dynamic chain-of-title sections (for example, if there are 9 title transfers, generate 9 sections instead of a fixed number) 4. Mapping Features - Complete mapping functionality - Display property-related mapping information - Integrate mapping data into the workflow where appropriate Ideal Candidate - Strong React experience - Experience working with existing codebases - Experience with AWS deployments - Experience with document generation and template systems - Ability to understand business workflows and recommend improvements - Strong communication skills Deliverables - Review existing application and provide assessment - Complete outstanding features - Test all functionality - Deploy updates to production environment - Provide documentation for future maintenance To Apply Please provide: 1. Relevant React projects you have completed 2. Experience working with AWS 3. Experience with dynamic document generation or template systems 4. Estimated availability 5. Your approach to taking over and completing an existing application We are looking for a long-term relationship with a developer who can continue improving the platform after the initial project is completed.

We're a trust-first local marketplace that connects parents with verified neighbors for school pickups, errands, and short-term childcare. We're pre-launch and finalizing our brand identity ahead of going live. We're looking for an experienced, hands-on logo and icon designer to deliver a polished, production-ready set of brand assets. THE SCOPE Four deliverables, in this order: 1. App icon — refinement and professional formatting We already have an app icon concept designed. We need it refined, vector-perfected, and professionally formalized — not redesigned from scratch. The final mark should hold up at every size from 1024×1024 down to 40×40. 2. iOS app icon — Icon Composer for iOS 26 (Liquid Glass) The refined icon must be properly built and exported in Apple's Icon Composer for iOS 26, with all required layers and treatments for Liquid Glass rendering across light, dark, tinted, and clear modes. You should already be familiar with Icon Composer and the iOS 26 icon system — please reference past work if you've shipped Liquid Glass icons. 3. Android adaptive icon The same icon, properly formatted as an Android adaptive icon (foreground and background layers, correct safe zones, tested across circle, squircle, and teardrop masks). 4. Favicon The icon adapted into a clean, legible favicon set (16×16, 32×32, 48×48, plus standard PWA and Apple touch sizes). Must remain recognizable at the smallest size. 5. Wordmark / text logo for the website (ground-up design) This is a from-scratch design to accompany the icon. We have loose direction — clean, lowercase, modern sans-serif, lightweight (not bold), to feel modern and trustworthy — but no locked design. We want a designer with a strong typographic eye to bring it to life. Custom letterforms or thoughtful refinement of an existing typeface are both welcome. Lockups (icon plus wordmark, horizontal and stacked) included. ABSOLUTE REQUIREMENT: NO AI This is non-negotiable and will be verified. — No AI-generated icons, favicons, or wordmarks. — No Midjourney, DALL·E, Stable Diffusion, Adobe Firefly, Recraft, Looka, or any generative tool used in the creation of the marks. — Hand-drawn / vector-built work only, in Figma, Illustrator, Glyphs, or equivalent. — We may ask to see process files (sketches, vector iterations, version history) before final payment. If you use AI in any part of the icon, favicon, or logo creation, do not apply. DELIVERABLES — Source files: .ai or .fig (editable, organized, named layers) — Vector exports: .svg, .pdf — Raster exports: .png at all required sizes for iOS, Android, web, favicon — Icon Composer file (.icon) ready for Xcode — Android adaptive icon assets (foreground and background layers) — Wordmark in all standard formats and lockups (horizontal, stacked, icon-only, wordmark-only) — Brief usage guide (1–2 pages): clear space, minimum sizes, color values, what not to do ——— TO APPLY, PLEASE INCLUDE 1. Portfolio links — specifically: app icons you've shipped to the App Store or Play Store, and wordmark / logo work. 2. Icon Composer experience — confirm you've shipped icons using Icon Composer for iOS 26 / Liquid Glass. Link to a live example if possible. 3. Confirmation of no AI use — please state this explicitly in your application. 4. Estimated timeline and fixed price for the full scope above. 5. One sentence on what you'd want to know before starting. Applications without portfolio links or that don't explicitly address the no-AI requirement will not be considered. TIMELINE AND BUDGET Looking to kick off within the next 1–2 weeks. Open to your fixed-price proposal — please include milestones (concept → refinement → final delivery). We value thoughtful work over speed, but we are pre-launch and time-sensitive. Looking forward to seeing your work.

I have a fully built, live React web app that currently stores all data in the browser's local storage. I need an experienced developer to migrate it to a real cloud backend using Supabase so data syncs across devices and is secure per-user. This is a well-defined project, I have a complete written spec (data schema, every storage key mapped to a proposed table, security requirements, and phased milestones with acceptance criteria). You will not have to reverse-engineer anything. I'll share the spec with shortlisted candidates. Scope - Set up Supabase (Postgres, Auth, Storage) - Replace the current local-storage data layer with Supabase - Implement real user authentication (replacing a placeholder login) Enforce Row-Level Security so users can only access their own data Move photo/document files to Supabase Storage with matching access policies - Preserve offline-first behavior with sync-on-reconnect - Deliver against clearly defined, testable milestones You're a great fit if you have: - Strong experience with Supabase (or Postgres + auth + RLS) and React - Shipped at least one production app with per-user data and real authentication - Can show me examples of Row-Level Security / multi-tenant data you've built - Clear communicator who works in defined milestones To apply, please: 1. Briefly describe a similar app you've built where users only see their own data, and how you secured it. 2. Tell me your experience specifically with Supabase RLS. 3. Give me a rough fixed-price range for Phases 1–4 (auth + core sync + files), understanding you'll refine it after seeing the full spec. 4. Include the word “moss" at the top of your reply so I know you read this. Budget: fixed-price by milestone, limited startup budget — looking for strong value, not the cheapest bid. Potential for ongoing work if the first phase goes well — including a larger analytics/admin dashboard build for the right person.

Overview SolisRx is a healthcare analytics consultancy embedded inside the operational core of mid-market infusion providers and specialty pharmacies. We sell monthly engagement retainers and deliver fractional teams across data engineering, decision analytics, and revenue cycle intelligence. Our clients run tens to hundreds of millions in annual revenue. Our recommendations move it. We are hiring a Principal Healthcare Analytics & AI Consultant to own client engagements end to end, from stakeholder discovery through delivery, expansion, and long-term account health. This is the senior IC seat in our delivery org. You will operate as the most senior voice in the room with clients, with direct access to the founder and direct authority to direct engineering resources. The bar for this role is high. The compensation reflects it. The trajectory is uncapped. What You Will Own Stakeholder discovery. Run scoped interviews with C-suite leaders at infusion centers and specialty pharmacies (COOs, CFOs, Heads of Operations, and occasionally medical directors). Translate ambiguous business questions into structured analytical problems. Produce decision-ready specs without supervision. End-to-end delivery. Architect and build dashboards, semantic models, and pipelines yourself across Power BI, SQL, and the Microsoft Fabric stack. You write the DAX, model the fact-and-dimension tables, validate against source. You do not hand off and supervise. Engineering leverage. Direct offshore engineering resources to scale your output. Write the spec. Run the QA. Own the outcome, and the bug. Executive presentation. Present findings to client executives without a Principal in the room filtering your work. Numeric, specific, recommendation-led. Account expansion. Identify scope-expansion opportunities within your account: new analytics workstreams, additional service lines, deeper RCM integration. Surface them to the founder with a clear business case. Help close them. Delivery system design. Beyond your own account, contribute to SolisRx's delivery operating model, sprint structure, QA standards, ticketing discipline, documentation conventions. We are still building the firm; senior ICs help shape it. This is a hybrid consulting and technical delivery role inside a healthcare-specific operating context. The work is roughly 70–80% data and BI craft: dashboards, modeling, pipelines, advanced intelligence & executive translation, and 20–30% healthcare domain fluency around revenue cycle, claims, prior auth, and infusion-specific operational realities. You will be the senior voice in the room for your account from week one. What We Are Looking For We screen on three dimensions: track record, technical fluency, and operating temperament. All three are required. Track record 8 to 13 years of progressive experience in BI, analytics, or data consulting Consulting background at a pharma or RCM analytics firm: ZS, Axtria, Beghou, IQVIA, MathCo, Trinity, Huron, Chartis, L.E.K. Healthcare, or Big 4, boutique, or independent. Senior IC role at a healthcare data startup or product company also a strong fit Current or recent title at the level of Decision Analytics Manager, Senior Manager, Associate Director, Principal, Staff, Architect, or Lead. If you are on the cusp of a pure people-management promotion and want a different path, we want to talk Demonstrable record of shipping engagements that drove client P&L outcomes, not just deliverables that "went well" internally Real client-facing experience: discovery with COOs and CFOs, executive presentations with no Principal filter in the room, managing stakeholders who disagree with each other Technical fluency Deep hands-on skill in Power BI or Tableau at a level where you have built things people thought were impossible. You know DAX or LOD expressions cold Strong SQL: CTEs, window functions, performance tuning, comfort debugging codebases you didn't write Experience shipping production ML use cases: classification, regression, or unsupervised, that drove clear business value. Not Kaggle notebooks. Real models that informed real decisions Comfort with the modern data stack, exposure to Microsoft Fabric, Databricks, Snowflake, dbt, or equivalents. Conceptual fluency in medallion architecture and lakehouse design Active, hands-on use of AI tools in your workflow. Claude, Cursor, Copilot, ChatGPT. You have shipped work using agentic frameworks, function calling, tool use, or RAG done properly, or you are itching to. Bias toward "Claude-pilled" curiosity. Operating temperament Recommendation-led, not options-led. You do not surface choices without a point of view First-principles problem structurer. Comfortable in ambiguity, undeterred by missing information, capable of converging on a defensible answer Comfort directing engineers and unblocking them, not just handing off specs Strong written and verbal communication. You write with precision, speak with confidence, and do neither at unnecessary length High-velocity executor. You self-impose deadlines and hold them. You flag slippage before it happens, not after Strong pluses Healthcare, specialty pharmacy, infusion, or RCM domain experience. If you have done commercial analytics, patient services, claims, prior auth, or benefits investigation work, we want to talk. Not required if you have led complex analytics engagements in other regulated industries Familiarity with 837/835, HL7, FHIR, X12, NCPDP etc. Previous Forward Deployed Engineer or embedded consultant experience inside a product company Prior tenure inside a high-bar environment: top consulting (MBB, ZS, IQVIA), top tech (FAANG analytics, frontier AI labs), or a venture-backed analytics startup What This Is Not This is not a back-office developer role. It is not a dashboard factory role This is not a pure people-management track. We are hiring a senior IC, not a manager-of-managers. If you are looking to step out of building, this is the wrong seat This is not a 9-to-5, but also not ibanking. We run on US Eastern hours and Client deadlines and urgency are real. The work will fluctuate but expect an average of 45-55 hrs/week. This is not a role with a 6-month ramp. You should be productive on a live account within your first two weeks This is not a domain-agnostic analytics role. You will be steeped in healthcare data, claims, eligibility, referrals, prior auth, billing, within your first 60 days. Candidates who cannot get excited about healthcare operational data should self-select out Trajectory Year 1: Embedded on a single high-priority account. Own a vertical slice of delivery. Founder shadows closely. Year 2: Lead a forward-deployed team end-to-end, own the engagement outcome. Present to client executives without filter. Profit-share begins. Year 3+: Senior leadership track. Profit-share moves from initial participation to a meaningful, growing stake tied directly to firm performance. Compensation This is structured for senior ICs who want upside, not predictability. Base: $115K–$140K, calibrated to demonstrated caliber. Performance-based variable: 20-30% of base for top performers, tied to client outcomes, delivery quality, and business performance. Total compensation range: $140K–$185K annually. Profit share: : Participation begins in Year 2 and grows into a meaningful stake as you move onto the senior leadership track. This is the principal-track-equivalent path inside a small, fast-growing firm. For US candidates: Healthcare and reasonable PTO, and full AI tooling budget. Fully remote with occasional client travel (roughly 4 to 8 US trips per year). If you're optimizing for guaranteed cash, the bigger firms will pay you more. If you're optimizing for trajectory and uncapped upside on a small, fast team, this is the structure. We offer visa sponsorship for exceptional candidates Process A real process designed to test for the work, not for interview trivia. Typeform application: we read every Typeform before any resume, here is the link to start: https://form.typeform.com/to/rRYHQzvq 30-minute discovery conversation with the hiring lead: understand you as a person beyond your resume 60-minute technical deep-dive Potential Paid take-home (~6 hours): a scoped analytical and technical exercise with a real-world deliverable. You present back Reference checks and offer