ABOUT THE PROJECTS. I run a curated marketplace on Shopify (The Ever Good) and I am building out an AI automation system to handle routine tasks in the business. I am AI-savvy and have built a Python agent myself, so I understand what I am asking for. I have the architecture planned and the business requirements semi-documented for each piece. I simply do not have the time to build everything I want to build, which is why I need a developer to work alongside me. The first project is a product review collection and import system. If it goes well, there is ongoing work building out additional agents over time, one at a time. This is a potential long-term engagement depending on how the first project goes. WHAT WE ARE BUILDING. The overall system is a set of AI agents that handle specific business tasks and route outputs to a simple dashboard where I can review, approve, and trigger actions before anything goes live. The dashboard is a Lovable build that gives me a single place to monitor agent status, review outputs, and approve or return anything that needs a human decision before it moves forward. Agents are planned across several areas of the business. We will build one at a time. I will walk you through the requirements for each before you start. Examples of agents here by business category (these could change): - MARKETPLACE & CATALOG. Product Reviews (first project), Catalog Enrichment and SEO, Pricing and Margin Monitor, New Product Auto-Pricer, Maker Stories, Maker Audit, Maker Analytics, Review Monitor. - CONTENT & SOCIAL. Content Generation, Cultural Moment Monitor, Social Publishing, Pinterest Curator, Instagram DM Automation, Image Production, Founder Content Amplifier. - MARKETING & ADS. Email Sequences, Paid Media Director, Ads Performance Monitor, LinkedIn Outreach. - SEO and Search. SEO and AI Search Visibility, Crawl Error and Redirects. - THE SCHOOL (Our Coaching Offerings). AI Readiness Assessment, Coaching Prep Tool, Workshop Launcher, Course Completion Monitor, Immersion Round Tracker. - FINANCE & OPS. Profit Police, Cash Flow Forecaster, Financial Health Monitor, System Health Monitor. - CUSTOMER SERVICE & GIFTING. Customer Service Drafts, Gift Inquiry and Proposals, Basket Assembler. OUR TECH STACK (Could Change). - AI AGENT BUILDING STACK. Claude Code, Claude API, Python, Make.com, Replit, Lovable, Google Sheets API, Baserow. - OTHER BUSINESS SYSTEMS. Shopify API, DropCommerce API, Matrixify, Typeform, Stripe API, Yotpo API, Klaviyo API, Instagram Business API, Later API, Pinterest API, ManyChat API, Bannerbear API, LinkedIn API, Google Analytics 4 API, Google Search Console API, DataForSEO API, QuickBooks Online API, Google Drive API. HOW WE WORK. - HOURLY. Collaborative and iterative engagement. - REQUIREMENTS. We review together before each build and refine as we go. - QA. I handle testing and QA on my end. - DOCUMENTATION. All work is documented throughout with decision logs and handoff notes so full ownership and control remains with me at every stage. - IP. All intellectual property and work product belongs to me entirely. - CLAUDE. You are expected to maintain your own Claude environment at a level that supports serious development work with no usage limitations. - ACCESS. All business systems and APIs provided with scoped credentials as needed. - DEPLOYMENT. Production deployment is handled collaboratively. - COMMITMENT. Looking for someone who can help maintain and evolve these tools over time while I retain full control and understanding of everything we build. WHAT I AM LOOKING FOR. - CLAUDE. Must use Claude as your central AI LLM. Experience. Working experience with the Claude API and the tools in the building stack above, or a demonstrated ability to learn new tools quickly. - COMMUNICATION.Clear communicator who works independently and does not need to be managed through a task, but is promptly responsive to me. - MINDSET. Building with AI tools as a regular part of your work. TO APPLY. Please share a brief description of one or two AI agents you have built, what they did, and what tools you used. Include a note on your familiarity with the tools listed above and your hourly rate.

Senior Mobile SaaS / Unity Entitlements Engineer for B2B Licensing Platform Project Overview: Simcoach Games develops behavioral health and educational games used by clinics, schools, clinicians, and families. We are looking for a senior technical resource to help us design and build lightweight access, licensing, and an entitlement layer for our Unity-based mobile games. Our current games are distributed through the Apple App Store and Google Play. We need to evolve from separate consumer and enterprise app versions toward a cleaner model where games can be downloaded easily, while access is controlled through parent purchases, clinic/school licenses, organization activation codes, or other entitlement rules. This is not a game development project. We are looking for someone with experience building mobile SaaS infrastructure, app-store purchase flows, backend entitlement systems, and simple admin tools. Scope of Work: The initial engagement will focus on one representative game and should produce a reusable pattern that can later be applied across our game portfolio. The expected scope includes: Recommend architecture for B2C and B2B access control across iOS and Android Design an entitlement model for organizations, users/devices, games, licenses, activation codes, expiration dates, and access rules Implement or integrate app-store purchase handling for parent/consumer unlocks Implement a clinic/school activation flow, such as organization codes or device activation Build a lightweight backend entitlement service Build a simple internal admin portal for Simcoach staff to create organizations, issue/revoke access, manage license status, and view activations Create a reusable Unity integration package or pattern that our internal developers can apply to other games Document the architecture and implementation clearly for future development Architecture must be compatible with future HIPAA compliance (encrypted data at rest and in transit, audit logging, BAA-ready cloud hosting). We will engage a HIPAA attorney separately, but the infrastructure should not create compliance debt. Advisory (Ongoing): Guide our team on App Store consolidation: merging duplicate listings, applying for Apple Unlisted App Distribution, configuring Apple Business/School Manager volume purchasing, and Google Play enterprise distribution. Recommend architecture for future integrations with ABA practice management platforms (CentralReach, Motivity, RethinkBH) via REST API/SSO. Ideal Experience: Strong mobile SaaS architecture experience Apple StoreKit and Google Play Billing experience, or experience with RevenueCat or similar tools Unity/C# integration experience Backend/API development experience using Firebase, Supabase, AWS, or similar platforms Experience with authentication, entitlements, activation codes, license management, and admin portals Familiarity with privacy-sensitive healthcare, behavioral health, or education products Ability to design pragmatic solutions for a small startup with limited engineering and support resources Helpful but Not Required: Experience with healthcare, digital therapeutics, behavioral health, edtech, or serious games Familiarity with HIPAA/FERPA-aware product design Experience with shared-device or clinic/school deployment models Experience supporting both direct-to-consumer and enterprise customers from the same mobile app What Success Looks Like: A successful engagement will give Simcoach a practical, scalable, and maintainable access model that reduces app-store confusion, avoids manual account administration, supports B2B clinic and school sales, and preserves a viable path for parent/consumer purchases. We are looking for a senior, pragmatic resource who can help us make the right architectural decisions, implement an MVP, and leave our internal team with a reusable foundation.

We are looking for a hands-on Forward Deployed AI Engineer to help build practical AI systems This is not a pure backend role and not a strategy-only consulting role. You will work close to end users, understand how their workflows actually operate, and then build AI-enabled tools that solve specific business problems. The ideal person is a strong software engineer who is comfortable with ambiguity, can communicate clearly with non-technical stakeholders, and can take an AI prototype from idea to something reliable and usable. What you will do - Learn the business workflows, systems, data, and constraints. - Build AI applications using Claude or similar large language models. - Use the right mix of prompting, retrieval, tool use, agents, and workflow automation. - Own delivery from scoping through prototype, testing, hardening, and handoff. - Create evaluations to determine whether the system is accurate, reliable, and safe enough to use. - Translate between domain experts and technical implementation. - Work carefully with sensitive or regulated data. - Document what you build so it can be maintained and reused. What we are looking for - Strong Python engineering skills. - Hands-on experience building with LLMs, preferably Claude or the Anthropic API. - Experience with RAG, structured prompting, tool use, evaluation, or agentic workflows. - Ability to operate independently in a messy, ambiguous environment. - Strong communication skills with both technical and non-technical stakeholders. - Track record of shipping working software, not just demos. - Comfort working with real-world data, integrations, and imperfect requirements. Helpful but not required - Prior forward deployed engineering, solutions engineering, or technical consulting experience. - Experience building AI tools for enterprise customers. - Experience in regulated or sensitive-data environments. - Familiarity with validation, auditability, traceability, or compliance-oriented workflows.

We are seeking an experienced developer to help build the first phase of a luxury storytelling and memory-preservation platform called Signature Story™. Signature Story™ combines premium printed keepsakes with personalized digital experiences accessed through QR codes. The goal is to create an emotional experience that allows recipients to view photos, videos, voice recordings, and personalized stories in a beautiful and intuitive format. Phase 1 Scope: • Mobile-responsive landing pages • QR code integration • Photo galleries • Video playback • Audio/voice message playback • Download functionality • Elegant luxury user experience • Basic content management capability Future Features (Not Required for Phase 1): • User accounts • Customer dashboard • Family memory archives • Memorial guestbooks • Timestamped visitor messages • Subscription functionality Ideal Candidate: • Experience building custom web applications • Experience with media-rich websites • Strong front-end design implementation • Experience working alongside designers and creative directors • Ability to build scalable architecture • Excellent communication skills Please provide: • Relevant portfolio examples • Technologies you recommend • Estimated timeline • Questions you would have about the project We are looking for a long-term development partner, not simply a one-time contractor.

I’m looking for a developer to help build a custom headless Shopify integration for a fashion e-commerce website. Overview I’m currently using Shopify (Grow plan) as the backend for all product management. All products, variants, pricing, and inventory are already fully set up in Shopify. The frontend is being designed entirely in Readymag, and I want full flexibility over the UX and shopping experience. The goal is to create a custom retail website experience similar in flow and interaction to: https://oddli.com/ What I need built The developer will help connect Shopify to a custom Readymag frontend using the Shopify Storefront API (preferred) or an equivalent headless approach. Key requirements: Sync product data (products, variants, images, pricing) from Shopify into Readymag frontend Build a fully custom product page experience inside Readymag Implement a custom “Add to Cart” system (NOT Shopify Buy Button) Create a slide-out or overlay cart drawer where users can continue shopping Cart state must persist across pages/sections Ensure smooth transition from cart → Shopify checkout when ready Maintain Shopify as the backend for all commerce and checkout functionality Ensure responsive, fast, and stable UX Reference The website should function similarly in terms of shopping flow and interaction to: https://oddli.com/ Ideal developer Experience with Shopify Storefront API or headless Shopify builds Strong frontend integration experience (custom carts, state handling) Familiar with embedding or working within no-code/low-code platforms Able to build clean, minimal, design-sensitive commerce UX Notes This is a design-led project. The frontend is already being developed in Readymag, so the focus is on integrating Shopify functionality without disrupting the visual direction. my website is: https://theonethelabel.com/

About the Project We're looking for an experienced Salesforce developer to build a productized, dealer-installable managed package that enables bi-directional data flow between our platform and a dealer's Salesforce org — with zero custom development required per dealer. What You'll Build 1. Managed Package An AppExchange-style managed package installable in any customer's Salesforce org. Must be versioned, upgradeable, and centrally maintainable by our engineering team after handoff. 2. Inbound Webhook Handler Receive webhook events from our platform and land them as records in defined custom objects inside the customer's Salesforce environment. 3. Outbound Push to Our API Send data from the customer's Salesforce back to our REST API — lead/applicant data, status updates, and other customer-side events. 4. Credential and Connection Management Handle OAuth or API key exchange between the customer's org and our platform. Admins configure the connection once during setup. No hard-coded or shared credentials. 5. Configurable Landing Layer Our data lands in stable custom object schemas. Customers configure their own downstream automation (flows, triggers, field mappings to Lead/Opportunity/Account) on their side. Out of Scope (this phase) Custom dashboards or reports inside the package Customer-specific workflow automation Data migration Non-Salesforce CRM connectors Deliverables Architecture proposal — auth model, object schema, webhook handler approach, sync patterns Managed package — built, tested, and deployable Installation and admin configuration guide Security review readiness documentation (AppExchange listing) Handoff documentation for our engineering team Who We're Looking For Proven experience building Salesforce managed packages (AppExchange experience a strong plus) Comfortable with REST API integration, webhook ingestion, and OAuth/API key credential flows Able to deliver clean handoff documentation — our team will own this after engagement ends Bonus: experience integrating Salesforce with SaaS platforms in fintech or vertical software

Senior Python Dev to Productionize a PPTX Medical Report Automation Prototype Overview We are a medical imaging report provider (Brain & Spine Injury Imaging Experts). We have a working Python prototype that auto-populates branded PowerPoint (.pptx) medical report templates and exports them to PDF. We need a senior developer to productionize it into a reliable, deterministic, well-documented tool. This is an automation/scripting engagement, not a slide-design job. What you'll build Harden and refactor our existing Python + python-pptx prototype into production-quality code. Fill locked-layout PowerPoint templates from structured input data (JSON) — text fields, findings lists, figure captions, measurements, and image placement. Generate required charts programmatically (e.g., NeuroQuant regional-percentile bar chart) rather than pasting static images. Export pixel-consistent PDFs (Aspose.Slides acceptable) that render identically on every run. Build a validation script that checks each generated report against required rules (footer text, page count, required fields, figure/label integrity) and flags deviations. Adapt the same engine to a second report type (Thoracic Spine) after the primary TBI report is accepted. Determinism requirement The tool must produce byte-for-byte consistent output across runs on the same input — same fonts, same layout, same positioning. Please describe in your proposal how you guarantee deterministic rendering and handle font embedding/substitution. Known Sample Drift — Footer Must Be Corrected The attached sample reports contain intentional footer inconsistencies that must NOT be reproduced. The signature-block footer currently varies across pages (some pages show only "Board Certified Radiologist," others add "Fellowship Trained in Musculoskeletal Imaging"). This drift is a known defect in the samples. The AUTHORITATIVE footer is the version we will supply in the spec sheet, and it must be applied identically on every page of every report. Your validation script must detect and reject any page whose footer does not exactly match the approved footer text. Do not treat the samples as the source of truth for footer content — treat the supplied spec as authoritative. Compliance / data handling This project involves medical reports. All development and testing will use de-identified sample data and dummy files only; you will not receive real patient PHI. A mutual NDA is required before we share the prototype code, templates, or licenses. Final report delivery to our HIPAA-compliant ShareFile account is handled with sandbox/test credentials during development; production keys are connected by us. Optional Phase 6 — Automated ShareFile Delivery Add a step that uploads the final PDF to a specified folder in our HIPAA-compliant ShareFile (Citrix) account via the ShareFile REST API, using a configurable case-to-folder mapping. Build/test with a non-PHI test folder and scoped test credentials; production credentials supplied and connected by client. Include setup instructions. Milestones (fixed price, ~$5,000 total, negotiable) Paid proof-of-concept: regenerate one approved sample report from our prototype on your environment, matching our reference output (small milestone — go/no-go gate). Production refactor of the fill engine and template handling. Deterministic PDF export + font handling. NeuroQuant chart generation + figure/label integrity. Validation script (footer, page count, required fields, drift detection). Spine report adaptation. (Optional Phase 6: ShareFile delivery.) A completion bonus applies for full delivery within 10 days of the awarded start. Required skills Python, python-pptx, Aspose, Microsoft PowerPoint, automation, data visualization, JSON data handling. API integration (ShareFile REST) a plus. To apply, please answer: Have you built PowerPoint/PPTX automation with python-pptx and/or Aspose? Share an example. How do you guarantee deterministic, pixel-consistent PDF output (fonts, layout)? Have you integrated the ShareFile (Citrix) API or similar OAuth-based file-storage APIs? Estimated timeline to complete Milestones 1–5. Attachments: De-identified sample reports (TBI and Spine) are attached for reference. Prototype code, real case data, and Aspose licenses will be provided after the NDA is signed.

We're looking for a Salesforce Developer / Architect to support a variety of client projects focused on custom development, integrations, automation, and revenue operations workflows. This role is ideal for someone who enjoys working directly with stakeholders, owning technical solutions end-to-end, and helping clients optimize their Salesforce ecosystem. Responsibilities: • Apex development, triggers, batch jobs, and Lightning Web Components (LWC) • Build and maintain Salesforce integrations with third-party platforms • Design scalable automation using Flows and Salesforce best practices • Support data migrations, data quality, and system optimization initiatives • Implement and enhance CPQ, Revenue Cloud, and quote-to-cash workflows • Collaborate with client stakeholders to gather requirements and deliver solutions Preferred Experience: • Salesforce CPQ and/or Revenue Cloud • Billing and payment platform integrations (Chargebee, Stripe, Zuora, etc.) • Salesforce ↔ HubSpot integrations • REST/SOAP APIs and middleware platforms • AI or automation experience is a plus Requirements: • 5+ years of Salesforce development experience • Strong Apex and LWC expertise • Experience with complex integrations and data migrations • Excellent communication and client-facing skills • US-based preferred/ No Agencies Side note: Please do not contact Joe or the hiring manager directly by email or phone regarding this role, as those outreach attempts will be treated as spam. All applications should go through the proper application process only.

What this is: I'm the founder of a working AI SaaS platform (FastAPI/uvicorn backend, React/Vite frontend, deployed on AWS). The product pipeline is built and live! I need an experienced engineer to build the authentication, payments, and usage-entitlement layer that gates the product behind login and paid usage. You'll work against a runnable stub repository (real routes + data shapes, proprietary internals removed) - so you can build and test the full layer without ever touching the core IP, and afterwards - I will merge your work into the production app! Scope: • Auth (Clerk): signup/login, session lifecycle, backend session/JWT verification, inject a validated `user_id` into protected endpoints. • Payments (Stripe): Checkout for purchasing usage credits, plus a webhook that credits the user's ledger on successful payment. The webhook MUST be signature-verified, idempotent (Stripe retries-credit exactly once), and reconcilable (handle webhook-failed-but-payment-succeeded). • Entitlement ledger (the core): a credit balance per user with atomic check-and-decrement (two concurrent requests must never double-spend) on PostgreSQL. A `check_entitlement(user_id, ...)`gate that expensive endpoints call before doing paid work. • Server-side route gating: enforce entitlement on every paid endpoint (not just hidden in the UI); clean 401/402/403 responses. • Frontend integration (React): login/signup UI, buy-credits/checkout flow, balance display,graceful "out of credits" states, wired to the above. • Tests for the money-critical paths (webhook idempotency, atomic decrement, gating-bypass attempts). Stack you'll work with: Python 3.11, FastAPI, Pydantic, uvicorn (Linux). React + Vite, Tailwind. PostgreSQL. Clerk. Stripe. Who I'm looking for: Someone who has shipped this exact kind of system to production before. In your proposal, briefly tell me: 1. How you ensure Stripe webhook idempotency and handle reconciliation when a webhook fails but payment succeeded. 2. How you'd implement the atomic credit check-and-decrement so concurrent requests couldn't double-spend. 3. A relevant production system you've built (Stripe + auth + usage metering ideally). *I'd much rather a short, specific proposal - than a long generic one!* Working with me: I'm an engaged founder who genuinely enjoys building, and I want this to be a good experience for both of us! I'm responsive, communicate clearly, and I respect your expertise - because you're the specialist here,and I'm hiring you because you know this much better than I do! I'm not a micromanager and I'm not nitpicky - I just want the end results to be solid! I review in milestones, asking questions because I like understanding the work (not because I'm second-guessing you), and I make decisions quickly so you're never stuck waiting on me! The scope is already well-defined (detailed spec + a runnable stub repo on engagement), so you're not pricing around a vague, shifting target - it's a clean, bounded build. I care about getting the money-handling pieces right, and I'm betting you do too - if that resonates, I think we'll work well together! IP / engagement: A mutual NDA + IP-assignment (work-for-hire) before repo access. You build against stubs; you won't receive the proprietary pipeline. Work is milestone-based, fixed-bid preferred. To apply: Answer the three questions above + share 1-2 relevant examples, and ballpark your timeline and milestone structure (suggested: auth → payments+webhook → ledger+gating → frontend → tests/docs)!

We are looking for an experienced HubSpot Sales Hub Professional implementation specialist / RevOps consultant who can move quickly and help us get HubSpot fully set up as our sales command center. We are a B2B restaurant equipment and supply dealer with both sales-assisted quoting and e-commerce. We recently purchased HubSpot Sales Hub Professional and need it implemented properly, but we also need it done quickly. We have spoken with several HubSpot Solutions Partners, and many are quoting timelines of 8 to 10 weeks. That does not work for us. We are looking for someone who can start immediately and help us launch a functional first version within 2 to 3 weeks. This is not a basic app-connection project. We need someone who can think strategically, design the CRM structure, clean up data, build workflows, integrate key systems, create dashboards, and make the system simple enough for our sales team to actually use. Generic proposals will be ignored. Please include the phrase “HubSpot fast launch” in the first sentence of your proposal so we know you read this. Main goal: We want HubSpot to become our daily sales cockpit. Our sales team should be able to log in and immediately know: - Who to call - Who to text - Who to email - Which quotes need follow-up - Which leads are stale - Which deals are close to closing - Which customers need attention As the owner/manager, I need dashboards that show: - Pipeline by stage - Deal value - Sales rep activity - Quote follow-up compliance - Lead source performance - Closed won / closed lost deals - Stale opportunities - Calls, texts, emails, and tasks by rep - Shopify/e-commerce activity when relevant - Monday.com project status after a deal is won Systems we need connected or considered: - Dialpad - Monday.com - Shopify - Mailchimp - Excel / CSV contact lists Ideal timeline: We want a functional first version launched within 2 to 3 weeks, with cleanup, refinements, and more advanced automation continuing after launch. We understand everything may not be perfect on day one, but we need the core sales system live quickly. Phase 1: Fast Launch, 2 to 3 weeks - Core HubSpot Sales Hub setup - Sales pipeline - Deal stages - Contact, company, and deal properties - Lead source tracking - Basic data migration - Dialpad calling/texting setup - Basic Monday.com handoff - Sales sequences - Email templates/snippets - Rep task queues - Owner/manager dashboards - Basic sales team training Phase 2: Cleanup and Optimization - Advanced reporting - Deeper data cleanup and deduplication - Shopify optimization - Mailchimp/contact syncing strategy - More advanced workflows - Payment/invoicing workflow - Additional automation - SOPs and recorded walkthroughs - Post-launch support and cleanup Scope of work: 1. HubSpot Sales Hub Professional setup Set up and customize HubSpot Sales Hub Professional, including: - Sales pipeline - Deal stages - Lifecycle stages - Contact, company, and deal properties - Required fields - Lead source tracking - Sales ownership rules - Task queues - Templates - Snippets - Sequences - Workflows - Notifications - User setup and permissions The system needs to be powerful but simple. If the sales team finds it confusing, they will not use it. 2. Sales process and pipeline design Help us design a clean sales process. Possible deal stages may include: - New Lead - Qualified - Quote Needed - Quote Sent - Follow-Up Active - Verbal Yes / Pending Deposit - Deposit Paid / Closed Won - Handoff to Operations - Closed Lost We are open to your recommendations if you have a cleaner structure. 3. Dialpad integration We need Dialpad set up inside HubSpot for inbound and outbound sales communication. Requirements: - Inbound call logging - Outbound call logging - SMS/text logging - Click-to-call from HubSpot - Missed call task creation - Call outcome tracking - Call/text activity associated with contacts, companies, and deals when possible - Rep activity reporting - Manager visibility into calls, texts, and follow-up activity 4. Monday.com integration We use Monday.com for operations and project management. We want a clean handoff from sales to operations. Ideal workflow: When a deal is marked Closed Won or Deposit Paid in HubSpot, a project/item should be created in Monday.com with the key deal and customer information. Fields may include: - Customer name - Company - Main contact - Contact info - Deal amount - Salesperson - Quote link - Invoice/payment link - Project type - Estimated delivery/install date - Notes - Project status We would also like key Monday.com project statuses pushed back into HubSpot so sales and management can see project status without digging through Monday. 5. Shopify integration We use Shopify for our e-commerce website. We need HubSpot connected to Shopify in a way that helps our sales team follow up on high-intent customers without turning HubSpot into a messy product database. Important items: - Customer sync - Order/customer activity - Abandoned cart visibility - High-value cart/order alerts - Lead source tracking - E-commerce customer segmentation - Avoid duplicate contact creation - Avoid unnecessary product/SKU clutter inside HubSpot We have a large product catalog, so we need a thoughtful integration strategy, not a blind sync of everything. 6. Mailchimp integration / migration We currently have contacts in Mailchimp. We need help deciding whether to: - Keep Mailchimp connected short-term - Migrate contacts into HubSpot - Use Mailchimp only for broad email marketing - Eventually move more email marketing into HubSpot We need proper handling of: - Marketing contacts - Unsubscribes - Consent status - Duplicate contacts - Lists/audiences - Segmentation 7. Contact import and data cleanup We need contacts imported from: - Excel / CSV sheets - Monday.com - Mailchimp - Shopify/customer data Before import, we need help cleaning and deduplicating the data. Deduplication should consider: - Email - Phone number - Company name - Website/domain - Existing customer vs prospect - Lead source - Sales owner - Customer type We do not want a messy HubSpot database full of duplicate contacts and companies. 8. HubSpot payments / invoicing setup We want help setting up HubSpot invoicing/payments if it makes sense for our workflow. We would like the ability to send invoices and provide payment options. Important: We want to explore whether customers paying by credit card can be charged an additional 3% processing fee, but this must be set up in a compliant way. If HubSpot cannot do this properly, we would like recommendations for a better alternative, such as ACH/check discounting or separate payment terms. 9. Dashboards and reporting Build simple, useful dashboards for both sales reps and management. Sales rep dashboard should include: - Today’s tasks - Calls to make - Texts/emails to send - Quotes needing follow-up - Deals with no recent activity - New inbound leads - Active sequences - Open deals by stage Manager/owner dashboard should include: - Pipeline value by stage - Revenue forecast - Deals won/lost - Close rate - Average deal size - Activity by rep - Calls/texts/emails by rep - Quote follow-up compliance - Deals with no activity - Lead source performance - Shopify/e-commerce lead activity - Monday.com project status summary 10. Training and documentation We need the system to be easy for our salespeople to use. Please include: - Basic training for sales reps - Manager/admin training - Simple written SOPs - Loom/video walkthroughs if possible - Post-launch cleanup and adjustment period Ideal candidate: You should have strong experience with: - HubSpot Sales Hub Professional - HubSpot CRM architecture - RevOps - Sales pipelines - HubSpot workflows - HubSpot sequences - HubSpot reporting/dashboards - HubSpot data imports - Contact deduplication - Dialpad integrations - Monday.com integrations - Shopify integrations - Mailchimp integrations - Zapier or Make - B2B sales processes - Sales team training Bonus points if you have worked with: - Equipment dealers - Distributors - B2B e-commerce - Quoting-heavy sales teams - Sales-to-operations handoffs - Companies with both inbound and outbound sales What we do not want: We are not looking for someone who only knows how to connect apps. We need someone who can help design the structure, challenge bad ideas, keep things simple, and build a clean system our team will actually use. Please do not apply if your approach is just “sync everything and see what happens.” Please also do not apply if you cannot start immediately or if your timeline is 8 to 10 weeks. We need someone who can move quickly. Pricing: We are open to hourly or milestone-based pricing. We are not looking for the cheapest option, but we do expect the price to match the scope, timeline, and experience level. Please do not simply bid the maximum budget. In your proposal, include: 1. Your estimated hours or fixed project range 2. Your proposed milestones 3. What you would complete in the first 2 to 3 weeks 4. What should be pushed to phase two 5. Any risks, dependencies, or items that could increase cost Application questions: Please answer the following when applying: 1. Can you start immediately? 2. Can you launch a functional first version within 2 to 3 weeks? 3. Describe a HubSpot Sales Hub Professional setup you’ve completed that involved multiple integrations. 4. Have you integrated HubSpot with Dialpad before? If yes, what did you set up? 5. Have you integrated HubSpot with Monday.com before? If yes, what was the workflow? 6. Have you worked with Shopify and HubSpot together? How did you avoid unnecessary data clutter? 7. How do you approach contact deduplication before importing data into HubSpot? 8. What dashboards would you recommend for a sales manager managing a small B2B sales team? 9. What would your implementation plan look like for this project? 10. What would you need from us before starting? 11. What parts of this project would you launch first, and what would you push to phase two? 12. What is your estimated hourly, fixed project, or milestone-based pricing? Quality matters, but speed matters too. We need someone who can build this correctly without dragging it out for months.