Claude Code Developer to Build AI Sales App – CRM, Mapping & Automation

# Build Revive Sales Command — AI-Powered Sales Intelligence, Territory Management & CRM Application **Fixed-price project | $500 target budget | Worldwide applicants welcome | Detailed master blueprint already prepared** ## IMPORTANT: PLEASE READ BEFORE APPLYING I am looking for an experienced, highly efficient **Claude Code / AI-assisted full-stack developer** to build a functional sales intelligence and territory management application. **I have already completed extensive product planning with ChatGPT and created a detailed master development blueprint.** This includes the business requirements, product features, workflows, architecture recommendations, sales activity metrics, geographic coverage requirements, integration objectives, and implementation priorities. You will receive this existing master blueprint after shortlisting. I am not looking to pay someone to conduct weeks of discovery, create another requirements document, or simply design mockups. **I want someone who can use Claude Code and other modern AI coding tools to implement the application efficiently, test it, and deliver working software that I can continue modifying myself using natural-language instructions.** My target starting budget is approximately $500. I recognize that the complete production platform may require additional work, so I want two separate quotes: 1. **Complete application:** Your most competitive fixed-price quote for the full scope, with realistic integration and data-source assumptions. 2. **Functional first release:** The most substantial working application you can deliver for $500, designed to be expanded without rebuilding it. I am especially interested in developers who have already built similar applications with Claude Code and can reuse proven technical patterns, open-source libraries, and established integrations where legally permitted. --- # SECTION 1 — BUSINESS BACKGROUND I am the Regional Sales Manager for Texas and Oklahoma at Revive Regenerative, a company selling capital medical aesthetic equipment. Our salespeople visit medical spas, plastic surgeons, dermatologists, cosmetic practices, and other medical offices throughout two large states. Our success depends on finding qualified practices, understanding their current technologies, identifying product opportunities, arranging meetings and demonstrations, conducting productive field visits, following up consistently, and keeping our company's CRM accurate. Currently, these activities can involve several disconnected systems: CRM, maps, spreadsheets, web research, email, phone calls, and handwritten or dictated notes. I want **Revive Sales Command** to bring these activities together into a single, intelligent, mobile-friendly application. The long-term objective is an AI-assisted sales command center that helps representatives know: - Which practices should I pursue? - Which accounts have not been contacted or visited? - What equipment and services does each practice advertise? - Which Revive products may fit their business? - Who are the likely decision-makers? - Where should I drive today? - Which accounts can I visit between scheduled appointments? - What should I say when I walk in? - What follow-up should I send? - What activity needs to be recorded in Nuvue? - How is each salesperson performing? - Which territories and markets are being neglected? - What deals are most likely to close? The application must be designed around actual field-sales workflows, not simply a generic CRM template. --- # SECTION 2 — EXISTING WORK ALREADY COMPLETED I will provide a comprehensive master development blueprint created through extensive planning with ChatGPT. The existing planning covers: - Application concept and objectives - Target users and roles - Target medical specialties - Sales territory definitions - Product portfolio categories - Prospect discovery workflows - Competitive equipment intelligence - Territory coverage logic - Daily route planning - Activity tracking requirements - Voice-note processing - Outlook follow-up workflows - Nuvue CRM integration requirements - Management dashboards - Sales coaching and reporting - Suggested technical architecture - Development milestones - Security and ownership requirements **Your first responsibility is to review and implement the existing blueprint, not replace it with an expensive new discovery process.** If anything is technically infeasible, dependent on a paid API, or unavailable through an authorized integration, identify that limitation and propose the least expensive viable alternative. The specification is detailed, but it does not include finished application code, a configured database, API credentials, or guaranteed access to external systems. --- # SECTION 3 — APPLICATION USERS The application should support four primary roles. **Regional Sales Manager (RSM)** Oversees multiple territories, reviews performance, identifies neglected markets, manages pipeline, coaches representatives, and reviews regional forecasts. **Area Sales Manager (ASM)** Manages assigned accounts and territory activity, prospecting, appointments, demonstrations, routes, follow-ups, and pipeline. **Territory Manager (TM)** Performs similar field-sales functions within assigned geography and accounts. **Administrator** Manages users, roles, permissions, product content, system settings, integration configuration, and data quality. Users must be dynamically created, deactivated, reassigned, and managed. No current or former employee should be hard-coded into the application. --- # SECTION 4 — AI PROSPECT RADAR This is one of the most important long-term features. I want the application to systematically identify and organize potential customers across Texas and Oklahoma. ### Target specialties Include: - Medical spas - Plastic surgeons - Dermatologists - Cosmetic dermatologists - Facial plastic surgeons - Oculoplastic surgeons - Lipedema surgeons - Bariatric surgeons - Medical weight-loss practices - GLP-1 clinics - OB-GYN practices offering aesthetic or wellness services - Hair restoration practices - Laser clinics - Men's health practices - Women's wellness practices - Anti-aging clinics - Longevity clinics - Functional medicine practices - Hormone replacement clinics - Other relevant practices that may benefit from medical aesthetic equipment ### Geographic requirements The application must support prospect discovery throughout **all of Texas and Oklahoma**, not just the largest cities. This includes major cities, suburbs, smaller markets, and commercially relevant communities. Examples: **Texas:** Austin, Round Rock, Pflugerville, Georgetown, Cedar Park, Leander, Kyle, Buda, San Marcos, Temple, Belton, Killeen, Waco, San Antonio, New Braunfels, Houston, Katy, Sugar Land, The Woodlands, Dallas, Fort Worth, Plano, Frisco, McKinney, Arlington, Tyler, Longview, College Station, Bryan, Corpus Christi, El Paso, Midland, Odessa, Lubbock, Amarillo, Abilene, Wichita Falls, and other markets. **Oklahoma:** Oklahoma City, Tulsa, Norman, Edmond, Broken Arrow, Lawton, Stillwater, Enid, Muskogee, Bartlesville, Shawnee, and other markets. The geographic coverage system should be extensible and should not rely on a manually hard-coded list of only these example cities. ### Prospect data For each account, store where available and legally obtained: - Practice name - Physical address - Website - Phone number - Specialty - Business category - Publicly listed decision-makers - Public business contact information - Number of locations - Advertised services - Publicly advertised equipment - Prospect priority - Assigned salesperson - Research source links - Date last researched - Data confidence - CRM matching status The application should identify and merge duplicate records. ### Data-source requirements Use authorized APIs, permitted public sources, and compliant enrichment methods. Do not promise unrestricted scraping of Google Maps, LinkedIn, or other sites that prohibit it. The developer should explain which prospect data is available at no cost, which requires paid services, and which cannot reliably be obtained. The system must distinguish real discovered prospects from sample records. --- # SECTION 5 — PORTFOLIO GAP INTELLIGENCE For each practice, analyze publicly available information and suggest which Revive technologies may be commercially relevant. Our active portfolio includes products such as: - Avira RF - Retraction - Emulsify - iBlaze CO2 - Fraclight IPL - Colormax - Hydra SH - Other approved active portfolio products AgeJET and TensaMax are being discontinued and should not appear as active recommendations. Product information must be configurable through an approved internal product library rather than permanently hard-coded. ### Example A practice advertises RF microneedling but does not advertise a dedicated skin-tightening treatment. The application might identify Avira RF as a possible opportunity and recommend asking whether the practice currently offers a comparable tightening modality. It must **not** state that the practice definitely lacks that equipment simply because the website does not mention it. ### Required intelligence Each account profile should display: - Advertised treatments - Identified technologies - Potential competitive equipment - Likely product opportunities - Opportunity confidence - Supporting public sources - Suggested discovery questions - Suggested next steps - Research freshness Create a concise **30-second pre-call briefing** that helps the salesperson prepare immediately before walking into the office. All AI-generated recommendations should be clearly distinguishable from verified facts. --- # SECTION 6 — TERRITORY COVERAGE RADAR This is another major priority. I want an interactive geographic dashboard showing how effectively Texas and Oklahoma are being covered. The system should answer: - Which markets have not been visited recently? - Which cities have never received a documented visit? - Which accounts have been neglected? - Where are our strongest prospect concentrations? - Which markets contain active opportunities? - Which salespeople are responsible for each area? - Where should we spend more field time? ### Required capabilities Display an interactive map with color-coded geographic coverage. Support filters for: - State - City - Market - Salesperson - Account specialty - Prospect priority - Days since last visit - Never visited - Open opportunities - Pipeline value - Product interest Track both **account-level coverage** and **market-level coverage**. A visit to one practice should not imply that every prospect in that city has been covered. Allow management to configure overdue thresholds, such as 30, 60, 90, or 120 days. ### Example If a salesperson has not logged a verified visit in Kyle, Texas, for 122 days, the system should flag that market. If nearby Buda and San Marcos also have overdue accounts, it should recommend grouping them into an efficient field day. Days-since-visit calculations must use real stored visit dates. The prototype can demonstrate this using fictional account and visit records. --- # SECTION 7 — SMART DAILY ROUTE PLANNING Salespeople spend much of their time traveling between offices. I want the application to help build productive routes based on scheduled meetings, nearby prospects, account priorities, and travel efficiency. ### Required functions - Enter or import scheduled meetings - Select starting location - Identify nearby accounts - Add suggested cold-call stops - Optimize stop order - Show locations on a map - Open navigation directions - Mark stops completed or skipped - Log visit outcomes - Reschedule unfinished stops - Save and retrieve daily routes - Filter routes by territory or salesperson ### Sales activity objectives ASM and TM targets should default to: - 2 scheduled sales meetings per day - 15 in-person cold-call drop-ins per day - 20 outbound prospecting phone calls per day These targets should be configurable by role and individual. RSM targets may differ. The application should not confuse route suggestions with completed activity. Actual activity must be logged and verified through the application's normal workflow. For the initial prototype, a working map, account selection, route saving, and basic routing would be valuable. --- # SECTION 8 — ACCOUNT AND CONTACT MANAGEMENT Each account should have a comprehensive profile. ### Account profile fields - Practice name - Address - Website - Phone - Specialty - Assigned salesperson - Account status - Prospect priority - Last contact date - Last in-person visit - Next follow-up - Publicly advertised services - Known equipment - Potential product opportunities - Contacts - Activity history - Meeting history - Notes - Opportunity pipeline - CRM sync status ### Contact fields - Name - Title - Practice - Business email, where authorized - Business phone - Decision-making role - Product interests - Contact preferences - Follow-up history Users should be able to search, filter, add, edit, and update accounts easily from desktop or mobile. --- # SECTION 9 — VOICE-POWERED VISIT LOGGING After visiting an office, a rep should be able to dictate a summary instead of typing everything manually. Example: "Just met with Sally at ABC Aesthetics in Georgetown. She has an older RF microneedling device, is interested in Avira, and wants information on skin tightening. Her owner makes the final purchasing decision. Follow up next Tuesday and see if we can schedule a demo." The system should extract structured information: - Account - Contact - Meeting date - Visit type - Products discussed - Current equipment - Decision-maker - Interest level - Objections - Next action - Follow-up date - Suggested email The user should review and approve extracted details before saving. For the first release, typed notes with AI extraction are acceptable if speech-to-text cannot be completed within budget. The architecture should support adding microphone input later. --- # SECTION 10 — OUTLOOK AI EMAIL CONCIERGE I want a system that helps salespeople send appropriate personalized follow-up emails through their authorized Microsoft Outlook accounts. ### Example After a visit, a salesperson says: "Send Sally a thank-you email with approved Avira clinical information. Two weeks later, send approved before-and-after materials and invite her to a demonstration." The system should: 1. Identify the account and contact. 2. Draft an appropriate personalized email. 3. Select materials from an approved content library. 4. Show the draft for review. 5. Obtain explicit approval. 6. Send through an authorized Outlook connection. 7. Schedule subsequent follow-ups. 8. Record the activity. 9. Stop or adjust the sequence when a reply, meeting, opt-out, or other stop condition occurs. ### Compliance Only company-approved clinical materials and claims may be used. Do not invent treatment results or clinical evidence. Do not send real emails during testing. Provide opt-out handling, access controls, and appropriate audit records. ### Integration Microsoft Graph is the preferred supported integration approach, subject to company IT approval. For the prototype, working draft creation and a simulated send/schedule workflow are acceptable. --- # SECTION 11 — NUVUE CRM INTEGRATION Our company's official CRM is Nuvue. **Nuvue must remain the official system of record for CRM data.** I want Revive Sales Command to work alongside Nuvue rather than create a disconnected second CRM. The integration should eventually support authorized synchronization of: - Accounts - Contacts - Calls - Visits - Meeting notes - Follow-up tasks - Opportunities - Pipeline stages - Product interests - Relevant email activity The EVP of Sales should retain appropriate visibility into account activity and pipeline through Nuvue. I have heard that a Claude/Nuvue connector may be available, but its capabilities have not yet been independently verified. **Developer responsibility:** Investigate available supported integration methods, authentication, read/write permissions, and deployment limitations. Do not assume that a connector available inside Claude can automatically be used by a separate web application. If direct integration is not available, propose a documented alternative, such as authorized exports/imports or a supported API. The first release may use a clearly labeled simulated Nuvue integration. --- # SECTION 12 — PIPELINE MANAGEMENT AND FORECASTING Create a sales management view for opportunities involving capital medical equipment. Each opportunity should support: - Account - Assigned representative - Product - Estimated deal value - Pipeline stage - Expected close date - Probability - Next step - Last activity - Demo status - Financing status - Notes - Closed/won/lost outcome Create management views for: - Total pipeline - Pipeline by salesperson - Pipeline by product - Pipeline by stage - Forecast by month and quarter - Overdue opportunities - Opportunities with no next step - Recent stage movement - Closed revenue The system must not fabricate sales numbers or treat simulated revenue as actual company performance. Where Nuvue is connected, synchronization and source-of-truth rules must be explicit. --- # SECTION 13 — SALES ACTIVITY SCORECARDS The application should measure actual rep activity against configurable expectations. Metrics should include: - Scheduled meetings - Completed meetings - In-person cold-call visits - Outbound calls - Meaningful conversations - Product demonstrations - New opportunities - Follow-up tasks - Pipeline movement - Revenue results Support daily, weekly, monthly, and quarterly views. Managers should be able to compare performance against role-specific targets without changing application code. --- # SECTION 14 — AUTOMATED MANAGEMENT REPORTS Create a Regional Sales Manager dashboard that summarizes sales activity and territory health. ### Daily report At approximately **5:30 PM Central Time**, generate an activity digest containing: - Completed meetings - Completed drop-ins - Outbound calls - New opportunities - Follow-ups completed - Overdue tasks - Pipeline changes - Individual rep activity - Coaching opportunities ### Weekly territory review Generate a Monday report highlighting: - Markets overdue for coverage - High-priority accounts without recent activity - Prospect concentrations - Upcoming meetings - Recommended field priorities - Stalled opportunities The system should support configurable schedules and time zones. Reports may initially be displayed within the application rather than emailed automatically. --- # SECTION 15 — AI SALES ASSISTANT The long-term application should include an AI assistant that can answer questions using authorized application data. Examples: "Which 20 plastic surgery practices in Houston have the strongest potential for Avira?" "Show me markets that haven't received a field visit in 90 days." "Build me a route for tomorrow starting in Georgetown with my two scheduled meetings and 10 nearby high-priority prospects." "Which reps are behind on meetings this week?" "Draft a follow-up email for the doctor I met yesterday." "Show me all opportunities expected to close this quarter." The assistant must use real application records and available verified data. It should clearly disclose when information is missing or uncertain. It should not independently send emails, modify CRM records, or perform irreversible actions without appropriate authorization. --- # SECTION 16 — DESIGN REQUIREMENTS The application should feel like a modern professional SaaS platform. It should not look like a basic spreadsheet or generic admin template. ### Main navigation Suggested sections: - Command Dashboard - Prospect Radar - Territory Coverage - Smart Routes - Accounts - Contacts - Visit Notes - Email Concierge - Pipeline - Team Scorecards - Reports - Settings ### User experience - Responsive desktop and mobile layouts - Optimized for iPhone use in the field - Clear navigation - Fast account search - Easy activity logging - Interactive maps - Clear visual status indicators - Minimal unnecessary data entry - Useful filters - Accessible text and controls I want a working application, not a static design or screenshot. --- # SECTION 17 — RECOMMENDED TECHNICAL STACK I am open to sensible recommendations, but my preferred architecture is: **Frontend:** Next.js, React, TypeScript **Styling:** Tailwind CSS and a mature component library **Backend/database:** Supabase, PostgreSQL **Geographic queries:** PostGIS where appropriate **Maps:** Mapbox, Google Maps, or another suitable service **Authentication:** Supabase Auth or comparable secure authentication **AI:** Approved server-side AI API integrations **Voice transcription:** Supported speech-to-text provider **Email:** Microsoft Graph API **CRM:** Officially supported Nuvue integration, if available **Hosting:** Vercel or another reliable deployment platform **Source control:** GitHub **Development:** Claude Code, supported by conventional engineering review and testing The developer should choose the simplest maintainable architecture rather than overengineering the project. Avoid unnecessary paid subscriptions. Provide estimates of ongoing API, hosting, database, mapping, AI, and prospect data costs. My personal Claude subscription should not be assumed to cover AI requests made by a deployed application. --- # SECTION 18 — SECURITY AND COMPANY DATA The initial application must be built with fictional or explicitly authorized sample data. No real company CRM records, private customer information, employee information, email accounts, or credentials should be accessed without appropriate approval. Required safeguards include: - Authentication - Role-based access control - Secure credential storage - Server-side secrets - Database access policies - Input validation - Basic audit logging - Protection against unauthorized account access - Separation of test and production environments - No exposed API keys in frontend code - Backup and recovery instructions The developer must not request my personal passwords. Production integration and company deployment require appropriate authorization. --- # SECTION 19 — DEVELOPMENT APPROACH I want the developer to use Claude Code to accelerate implementation, but not simply generate code without testing it. The preferred process: ### Milestone 1 — Project foundation - Review master blueprint - Create project structure - Configure GitHub - Configure development environment - Establish database - Set up authentication foundation - Create navigation and design system - Run the application locally or in a safe preview environment ### Milestone 2 — Core sales application - Dashboard - Account management - Contact management - Sample data - Search and filters - Visit logging - Activity tracking ### Milestone 3 — Territory and routing - Geographic market records - Territory Coverage Radar - Days-since-visit calculations - Interactive map - Account assignment - Basic daily route builder - Route saving ### Milestone 4 — AI workflows - Prospect research architecture - Portfolio opportunity recommendations - Pre-call briefing - Note extraction - Email draft creation ### Milestone 5 — Integration preparation - Nuvue integration assessment - Outlook integration assessment - Mock adapters - API configuration documentation - Approved integration implementation where feasible ### Milestone 6 — Management and handoff - Pipeline views - Scorecards - Reporting - Testing - Documentation - Recorded walkthrough - Claude Code maintenance setup Please identify which milestones are included in each proposed price. --- # SECTION 20 — WHAT MUST ACTUALLY WORK I do not want a prototype where every button merely opens a decorative popup. For the functional first release, I want to be able to demonstrate real behavior. Examples: 1. Add a fictional medical spa account and save it. 2. Search for that account and open its profile. 3. Assign it to a salesperson. 4. Log a visit and save notes. 5. See the last-visit date update. 6. See the Territory Coverage Radar recalculate coverage. 7. Add accounts to a daily route. 8. Save and reopen the route. 9. Record calls and meetings. 10. See the activity scorecard update. 11. Create a follow-up task. 12. Enter visit notes and generate a draft follow-up. 13. View an opportunity in the pipeline. 14. Refresh the page and retain the saved records. If a feature is simulated, label it clearly. No fake claims of completed integrations, live prospect discovery, or production readiness. --- # SECTION 21 — CRITICAL: I MUST BE ABLE TO MAKE FUTURE CHANGES MYSELF This requirement is extremely important. I am not a programmer. After the developer completes the initial build, I want to open Claude Code and make requests such as: "Add a filter showing all practices that haven't been visited in 90 days." "Change the daily meeting goal for Territory Managers." "Add a new product to the portfolio." "Create a weekly report showing which markets are being neglected." "Change the dashboard layout." "Fix the account search problem." I want Claude Code to understand the application, modify the appropriate files, run tests, and prepare a preview for my approval. ### Developer handoff requirements Provide: - A clean GitHub repository owned by me or my company - A README with setup instructions - A CLAUDE.md file containing project architecture, coding conventions, and instructions for future Claude Code sessions - A PROGRESS.md file tracking completed and remaining functionality - A documented database schema - Environment variable instructions - Automated tests for important workflows - A simple preview/deployment process - A recorded screen-share demonstration - A plain-English maintenance guide **During the handoff, I want the developer to watch me make one actual application change using Claude Code.** The goal is to avoid needing to hire a developer every time I want to adjust a field, filter, report, or screen. I understand that complicated integrations, security changes, and production failures may still require professional support. --- # SECTION 22 — SOURCE CODE AND OWNERSHIP All deliverables must be handed over to accounts controlled by me or my company, as appropriate. This includes: - Source code - GitHub repository - Database configuration - Application configuration - Deployment configuration - Documentation - Custom application assets - Integration code developed for the project Disclose all third-party libraries, licenses, and recurring services. Do not use proprietary starter kits or components that prevent me from maintaining the application without paying the developer indefinitely. I want the freedom to continue developing the application myself or hire another developer later. --- # SECTION 23 — BUDGET AND BIDDING **My target budget is $500 for the most substantial working first release possible.** I am specifically seeking someone who can use Claude Code and AI-assisted development to reduce traditional development costs. I am not looking for an agency charging for extensive project management, discovery workshops, or design presentations. I already have a detailed blueprint. Please submit two separate quotes: ### Option A — Full Application Provide your most competitive fixed-price bid to implement the complete vision described here. Break down the work into realistic milestones. Clearly state assumptions, exclusions, required external services, and ongoing costs. Do not quote a complete production application if the bid only includes a demonstration. ### Option B — $500 Functional First Release Explain the maximum functional scope you can deliver for $500. Prioritize: 1. Working application foundation 2. Professional dashboard 3. Persistent account/contact database 4. Territory Coverage Radar 5. Daily route planning 6. Visit/activity logging 7. Basic pipeline 8. Simulated AI/CRM/email workflows 9. GitHub ownership 10. Claude Code handoff If you cannot complete all ten within the budget, specify exactly which you can complete. I value a smaller fully working application over a larger collection of unfinished screens. I am open to continuing development in additional fixed-price milestones after reviewing the first release. --- # SECTION 24 — REQUIRED PROPOSAL QUESTIONS Please answer the following questions individually. **1. Claude Code experience** How many working applications have you built using Claude Code? Provide links to at least two relevant examples and explain your role. **2. Comparable projects** Have you built a sales CRM, territory management platform, geographic prospecting application, or AI workflow system? Please describe. **3. Complete platform price** What is your fixed-price estimate to deliver the complete application, and how long would it take? **4. $500 first release** What exactly can you deliver for $500? List the features that will work, features that will be simulated, and features that will remain incomplete. **5. Technical stack** Which stack would you use and why? What would you change from the recommended architecture? **6. Prospect discovery** What compliant sources or APIs would you use to find practices across Texas and Oklahoma? What coverage and recurring costs should I realistically expect? **7. Nuvue integration** How would you investigate and validate Nuvue CRM integration before promising it? **8. Outlook integration** Have you implemented Microsoft Graph authentication, email sending, reply monitoring, or scheduled follow-up sequences? **9. Maps and routing** Which mapping and routing services would you use, and what are their likely costs? **10. Ownership and handoff** How will you make it possible for a nontechnical owner to continue modifying the application using Claude Code? **11. Delivery and testing** How will you demonstrate that features actually work? What automated tests will you include? **12. Ongoing costs** Estimate monthly hosting, database, AI, mapping, email, and prospect data costs separately from your development fee. **13. Support** What post-delivery bug-fix period do you include? What would occasional future support cost? **14. Timeline** When could you start, and when could you demonstrate the first working version? --- # SECTION 25 — HOW I WILL SELECT A DEVELOPER I will prioritize: - Demonstrated working applications - Strong client reviews - Real Claude Code experience - Practical full-stack development skills - Competitive fixed-price proposals - Clear communication - Honest technical estimates - Willingness to use my existing blueprint - Ability to deliver maintainable software - Excellent handoff and documentation I am particularly interested in an independent developer who uses AI coding tools daily and can build efficiently. Please begin your proposal with: **REVIVE COMMAND** This confirms that you read the description. Generic proposals that do not address the actual requirements will not be considered. --- # FINAL PROJECT OBJECTIVE I want Revive Sales Command to become the central sales intelligence and territory management platform for our Texas and Oklahoma team. It should eventually help us identify more qualified prospects, improve territory coverage, make field days more productive, personalize follow-up, improve CRM compliance, and give management better visibility into performance. **The planning is already substantially complete. I need a talented developer to turn it into working software using modern AI-assisted development methods, at the most competitive realistic cost.** I am ready to share the complete master blueprint with shortlisted candidates and begin with a clearly defined fixed-price milestone.