Custom AI Business & Personal Assistant – Full Automation and Ownership

# Custom AI Business & Personal Assistant – Full Automation and Ownership ## Project Overview I am looking for an experienced AI software developer to help design and build a custom AI-powered business and personal assistant. The goal is to create one cohesive assistant that I can communicate with naturally through text and voice. It should understand instructions, retain useful context, remember contacts and preferences, manage information, perform approved tasks, coordinate workflows, and handle multi-step activities across the services I use. This is intended to become a reliable, practical assistant that can perform real work—not simply a chatbot that answers questions or a collection of disconnected automations. I am not a technical person, so the developer must be capable of explaining the system in plain English, demonstrating functionality, and making it possible for me to test and use what is built without needing to understand the underlying code. **IMPORTANT – INITIAL PROJECT BUDGET: $350** The posted $350 budget is for the initial, separately scoped development phase only. It is not a budget for the entire system. The only work currently authorized is this initial phase. Any additional development would require a separate written proposal, price, scope, milestone schedule, and my approval. There is no commitment to continue beyond the initial phase. Please submit a proposal specifically explaining what you can deliver within this initial budget. ## 1. Overall Assistant Capabilities The long-term system should be designed to support: - Natural conversations through text and voice. - Understanding ordinary instructions without requiring technical commands. - Remembering relevant information, preferences, contacts, conversations, projects, and previous decisions. - Maintaining context across conversations and tasks. - Planning and completing multi-step activities. - Using approved integrations to access information and perform authorized actions. - Running approved tasks in the background. - Providing progress updates, completion reports, errors, and notifications when something needs my attention. - Allowing me to interrupt, redirect, or stop an activity. - Maintaining a record of completed actions and important decisions. - Handling multiple business and personal responsibilities through one cohesive interface. The assistant should be designed so that capabilities can be expanded over time without requiring the entire system to be rebuilt. ## 2. Accounts and Services to Support The system will eventually need to work with the following accounts and services: **Email** - Personal Gmail account. - Separate Gmail account used for brand outreach and collaborations. - Work Outlook account. **Files and productivity** - Google Drive. - Google Docs. - Google Sheets. - Google Calendar. - Apple Calendar. - iCloud Contacts. **Communication** - WhatsApp Business, used only for internal contractor communication. - A dedicated phone number with iMessage, SMS, and RCS support where technically and legally available. - Telegram where appropriate and supported. **Third-party portals** The system may need authorized access to approximately 14 portals, including Amazon, Castgen, Clear Capital, Equator, Google, Private Jury, Push Health, Trinity Online, TurboTenant, UpNest, Upwork, VDH NextRequest, ViralVue, and zipForm Plus. Access must use legitimate authentication and authorized integrations. No security bypasses, unauthorized access, or attempts to circumvent multi-factor authentication. Do not request passwords, API keys, or sensitive account credentials in the job proposal or ordinary messages. Secure access arrangements will be discussed after hiring. ## 3. Email and Communication Management The assistant should eventually be able to: - Monitor and synchronize the three email accounts. - Summarize unread messages and identify important communications. - Notify me about urgent messages and time-sensitive matters. - Draft and send replies within existing email conversations when authorized. - Identify follow-ups and unanswered messages. - Maintain useful contact history and communication context. - Prepare a morning briefing summarizing important messages, tasks, and upcoming events. - Send texts on my behalf through supported and authorized communication integrations. - Support inbound and outbound calls where technically supported and legally permitted. - Provide summaries of calls and communication activity where available. - Create reminders and calendar events based on conversations and instructions. Communication safeguards: - Do not send messages or make calls outside the permissions I establish. - Do not pretend to be me in situations where disclosure or identification is required. - Do not send bulk outreach without my explicit authorization. - Stop outreach when a recipient opts out, a message bounces, or a human reply requires attention. - Do not use WhatsApp for real estate clients or leads. - Do not automatically CC or BCC buyers or sellers on third-party emails. - Do not send calendar invitations or add attendees when creating calendar events. - Never automatically archive, move, or delete Outlook emails. - Gmail auto-archiving may be used only for my personal Gmail account and only under approved rules. ## 4. File Management and Administrative Work The assistant should eventually be able to: - Search, read, summarize, and organize files in Google Drive. - Extract information from PDFs, contracts, spreadsheets, receipts, and other documents. - Record relevant information in Google Docs, Sheets, or approved tracking systems. - Compare documents and identify differences in prices, terms, dates, initials, deadlines, and other important details. - Track receipts and business expenses for tax preparation. - Maintain separate personal and business file organization. - Maintain two existing Drive folder structures, including my personal files and the broker-shared folder titled "Hunter H Docs." - Identify missing documents and flag incomplete records. - Create reports and summaries that I can review. The assistant must not delete or permanently modify important documents without my explicit authorization. ## 5. Real Estate Business Workflows The system should eventually support my real estate business, including: - Researching county assessment records, GIS information, property plats, septic records, and well information. - Assisting with property research and listing preparation. - Drafting listing descriptions and marketing materials. - Preparing comparative pricing worksheets and CMAs. - Working with South Central MLS information and approved integrations where available. - Tracking transaction deadlines, earnest money, inspections, appraisals, title coordination, and closing changes. - Organizing transaction documents and maintaining property folders. - Comparing contracts and identifying changes or missing information. - Preparing showing packets using MLS sheets and plat maps. - Delivering showing packets by 6 PM on the evening before a scheduled showing when the required information is available. - Omitting lead paint forms and disclosure documents from those showing packets. - Preparing follow-up reminders and transaction summaries. Real estate communication safeguards: - WhatsApp must never be used for real estate clients or leads. - Do not send messages to buyers or sellers without the appropriate authorization. - Do not CC or BCC clients on third-party communications unless specifically instructed. - Client-facing communication must follow my established approval rules. - When drafting texts for me, use one continuous block of text, lowercase, minimal periods, and no greeting or signature unless requested. - Do not make legal, contractual, or financial commitments on my behalf. ## 6. Creator, Brand Outreach, and Contractor Workflows The assistant should eventually help manage creator and brand-related work, including: - Reviewing brand opportunities and campaign information. - Evaluating opportunities using available performance information and metrics. - Preparing personalized brand-retainer pitches. - Monitoring incoming brand replies and identifying opportunities requiring attention. - Updating outreach trackers. - Routing appropriate delegated follow-ups to my assistant. - Maintaining contractor instructions, standard operating procedures, and digital content calendars. - Tracking outreach activity and identifying duplicate or unsuccessful efforts. Outreach must follow approved schedules, daily limits, recipient restrictions, and applicable platform rules. No outreach campaign should be activated without my review and explicit approval. ## 7. Existing Automations and Recurring Schedules There are existing routines and schedules that may need to be recreated, improved, or integrated into the system. These include: - Priority email and communication alerts. - Hourly filing and organization checks. - A 9 AM morning briefing. - Calendar conflict checks. - Follow-up monitoring. - Email opportunity reviews. - Scheduled brand and property-inspection outreach. - Lead reply monitoring. - Outreach monitoring and daily summaries. - Transaction synchronization. - Drive folder checks and property folder audits. - Weekly local event research. - Weekly social media content preparation. - Monthly financial calculations for revenue, giving, and tax reserves. The schedules have specific timing, daily limits, quiet hours, and other conditions. A detailed schedule inventory will be provided during the project. **Do not automatically activate, recreate, or send any scheduled communication simply because it appears in an existing schedule.** First inventory the routines, identify what is technically possible, document any conflicts or limitations, and obtain my approval before activation. Quiet hours are generally 10:30 PM to 6 AM, with limited exceptions for requested security codes and genuinely due reminders. ## 8. Financial and Purchasing Safeguards The assistant may eventually help organize financial information, calculate totals, track expenses, and prepare financial summaries. However: - No money transfers. - No payments. - No purchases. - No financial account changes. - No commitments involving money. These actions require my explicit approval unless I later establish specific written permissions and limits. ## 9. Background Tasks and Web-Based Work The long-term system should be able to perform approved online tasks through authorized accounts and integrations. Examples include: - Checking third-party portals. - Retrieving information. - Updating approved records. - Monitoring prices and shopping opportunities. - Preparing shopping carts. - Tracking task status and reporting results. The developer must identify which actions can be performed reliably and legally through supported integrations and which require manual intervention. The system must never bypass authentication, security controls, or platform restrictions. ## 10. User Experience and Ease of Use I need a system that is practical for a nontechnical user. The finished system should include an intuitive interface where I can: - Type or speak instructions. - See what the assistant understood. - Review tasks that are in progress. - See completed tasks and results. - Approve or reject actions that require permission. - Correct the assistant or change its instructions. - Interrupt or stop a task. - Review errors and tasks requiring my attention. - Access relevant conversation and task history. The developer must demonstrate functionality in a way that I can personally test. A technical explanation or code repository alone is not an acceptable substitute for a usable demonstration. ## 11. Initial $350 Phase – Required Deliverables The first phase must be separately scoped and limited to the posted $350 budget. It must produce tangible results, not just a consultation or a presentation. The initial phase should include: **A. Requirements and feasibility review** - Review the requirements in this posting. - Identify what is technically feasible. - Identify limitations, unsupported services, and platform restrictions. - Identify any requirements that need a different approach. **B. Proposed architecture** - Explain in plain English how the system would be structured. - Identify the major components and how they would work together. - Explain how memory, integrations, permissions, and background tasks would operate. - Explain how the system can be expanded without locking me into the developer. **C. Integration and operating-cost plan** - Identify proposed third-party services, APIs, models, libraries, and software. - Explain which are free, paid, open source, or subject to usage charges. - Identify licensing and commercial-use restrictions. - Provide realistic estimated recurring operating costs and explain what affects those costs. - Identify any services that require separate subscriptions or accounts. **D. Security and ownership plan** - Explain how credentials and sensitive information will be protected. - Explain how access permissions will be controlled. - Explain how the system, code, data, and infrastructure will remain under my control. - Identify potential security risks and how they will be addressed. **E. Working proof of concept** - Build a small but real working demonstration. - It must use an actual approved integration or tool to perform an agreed task. - It must be interactive and testable by me. - It cannot consist only of screenshots, mockups, diagrams, prerecorded video, or a written description. - The exact task and pass/fail test must be agreed upon in writing before development begins. - The developer must demonstrate it live and walk me through testing it. **F. Handoff** - Provide the source code and configuration created for the proof of concept. - Place the work in a repository that I own and control. - Provide setup and operation instructions. - Provide a list of dependencies and their licenses. - Explain what is complete, what is not complete, and what would be required for a subsequent phase. The initial phase is not expected to build the entire assistant. It must demonstrate that the developer understands the project, can propose a sound approach, and can deliver working software. ## 12. Milestones, Payment, and Acceptance Requirements This project must use Upwork fixed-price milestones. The initial $350 phase should be divided into separately funded milestones. My preference is: - Milestone 1: $100 – Requirements review, feasibility, architecture, dependency and cost analysis, security and ownership plan, and an agreed proof-of-concept specification. - Milestone 2: $250 – The working proof of concept, demonstration, testing, source code, configuration, and handoff. Only the first milestone should be funded at the start. The second milestone will be funded separately after I have reviewed and accepted the first milestone. The following conditions apply to all milestones: 1. Each milestone must have a written description of exactly what will be delivered. 2. Each milestone must include objective acceptance criteria and test cases. 3. Each milestone must state what I will be able to see, use, or test when it is complete. 4. The developer must provide a live demonstration of working functionality when applicable. 5. The developer must provide the agreed deliverables before requesting payment. 6. Progress reports, screenshots, mockups, verbal assurances, or prerecorded videos alone do not qualify as completed deliverables. 7. I must have a reasonable opportunity to review and test the submitted work within the applicable Upwork review period. 8. If the work does not meet the agreed requirements, the developer must address the identified in-scope deficiencies before acceptance. 9. No additional features, services, subscriptions, or expenses may be added without my prior written approval. 10. No future milestone is automatically authorized because a previous milestone was completed. 11. I may choose not to continue after any completed phase. There is no obligation to hire the developer for future work. 12. All payments and milestone releases must follow Upwork's fixed-price payment and dispute procedures. No off-platform payments. Do not submit a milestone for payment if the agreed deliverables have not been provided. I will not release payment based solely on claims that work is substantially complete or that additional time is needed to finish agreed requirements. ## 13. Ownership and Intellectual Property – Mandatory I require full ownership and control of the custom work developed specifically for this project. This is a mandatory condition of consideration for the position. The agreement must provide for assignment to me, to the fullest extent legally transferable, of all rights in the custom work created and paid for under the project, including: - Source code. - Custom software. - Scripts and automations. - System architecture and custom configurations. - Database structures created for the project. - Custom prompts and workflows. - Documentation. - Interfaces and user-facing components. - Other custom deliverables created specifically for the project. I must have broad rights to use, modify, maintain, reproduce, distribute, license, commercialize, and resell the custom work. I do not want an arrangement involving developer ownership, equity, royalties, revenue sharing, or an ongoing license fee for custom work that I have paid to have developed. Any pre-existing developer-owned components must be disclosed in writing before they are used. I must be able to operate, modify, maintain, transfer, and commercialize the system without depending on the developer's continued involvement or permission. Third-party software, models, APIs, libraries, and services are not expected to become my intellectual property. However, their ownership, licenses, commercial-use rights, recurring fees, restrictions, and replacement options must be disclosed and approved before they are incorporated. No undisclosed proprietary dependencies are permitted. ## 14. Accounts, Infrastructure, and Administrative Control All essential accounts and infrastructure must be owned and controlled by me. This includes, as applicable: - Source-code repository. - Hosting and cloud accounts. - Database accounts. - Domain and related services. - AI provider accounts and API billing. - Integration accounts. - Backups and storage. - Monitoring and deployment services. - Credentials and administrative access. I must have administrator access from the beginning of the project. The developer may receive only the access necessary to perform authorized work. The developer must not create hidden accounts, retain exclusive administrative control, or make the system dependent on a personal account, private server, or developer-controlled API key. No hidden backdoors, remote shutdown mechanisms, undocumented services, access restrictions, or other features that could prevent me or another developer from operating the system are permitted. All credentials must be handled securely and must never be placed in public source code or ordinary messages. ## 15. Continuity, Documentation, and Developer Replacement The system must be built so another qualified developer can take over if necessary. The developer must maintain and provide: - Organized and readable source code. - Clear project structure. - Documentation explaining how the system works. - Installation and configuration instructions. - Deployment and restoration instructions. - Dependency and licensing records. - Database and backup information. - Instructions for maintaining and updating integrations. - Known limitations and unresolved issues. Work must be committed to my repository regularly rather than kept exclusively on the developer's computer. I must not have to rely on the original developer to access, operate, repair, or continue developing the system. At the end of each completed phase, all paid-for deliverables must be transferred to my control. At the end of the engagement, the developer must return or transfer all project materials and confidential information, cooperate with the agreed handoff, revoke their access when requested, and certify deletion of confidential credentials and data from personal systems, subject to any legally required retention. ## 16. Security, Privacy, and Data Protection The developer must take reasonable, documented security measures appropriate for a system handling personal, business, financial, and client-related information. Requirements include: - Secure credential storage. - Appropriate encryption in transit and at rest where supported. - Least-privilege access. - Separation of test and production environments where appropriate. - Secure handling of backups. - Appropriate logging and monitoring. - No use of my information for unrelated purposes. - No sharing, selling, publishing, or using my data to train or improve unrelated products or services. - No copying project data into personal or public repositories. - Prompt notification of any suspected security incident, unauthorized access, or data exposure. - No access to accounts or information beyond what I have specifically authorized. The developer must explain what information is stored, where it is stored, who can access it, and how it can be exported or deleted. ## 17. Developer Qualifications I am looking for someone with demonstrated experience in: - AI agent development. - Conversational AI and large language models. - API and third-party service integrations. - Workflow automation. - Python or other suitable programming languages. - Voice-enabled applications and speech integrations. - Secure application architecture. - Database design and persistent memory. - Building usable applications rather than only prototypes or demonstrations. Please provide: 1. Examples of comparable systems you have personally developed. 2. A description of your specific contribution to those projects. 3. Examples of working software that can be demonstrated. 4. Your proposed approach to this project. 5. Your experience with integrations, persistent memory, permissions, and background tasks. 6. Any relevant limitations or risks you see in the requirements. 7. Confirmation that you can work under the ownership, security, documentation, and milestone conditions described here. Do not submit examples of work that you did not personally build or substantially contribute to. ## 18. Future Development If the initial phase is successful, I may consider additional development in separately defined phases. Potential future phases could include: - Expanded email and communication management. - Persistent memory and contact history. - Voice functionality. - Calendar and file management. - Real estate business workflows. - Creator and brand outreach workflows. - Background task execution. - Additional portal integrations. - More advanced planning and multi-step task execution. - Production deployment, monitoring, and reliability improvements. These are potential future areas of work, not currently authorized deliverables. Each future phase must have its own written scope, price, schedule, milestones, acceptance criteria, and funding approval. I am not committing to a larger project or ongoing contract at this time. ## 19. How to Apply Please address the following in your proposal: 1. What would you deliver within the initial $350 phase? 2. What specific working proof of concept would you recommend, and what would I be able to test? 3. How would you divide the initial phase into milestones? 4. How would you ensure that I own and control the code, accounts, data, and infrastructure? 5. What third-party services or recurring costs do you anticipate? 6. What are the most significant technical limitations or risks you see? 7. How would you make the system maintainable and transferable to another developer? 8. What comparable work have you personally completed? Please be realistic and specific. I am not looking for someone to promise that the entire system can be built within the initial budget. I am looking for a qualified developer who can establish a sound foundation, demonstrate real working capability, communicate clearly, and deliver work in verifiable stages. **The initial $350 phase is the only currently authorized work. Any additional work requires my separate written approval.**