Description
Summary We are seeking a senior AI SaaS architect, supported by a capable development team, to design and build a secure AI-enabled project management and engineering operations platform. The platform will be called the: Hammad Engineering Command Center We operate a specialized fenestration and façade engineering business with local client-facing project managers and an established remote technical team of engineers, designers, and drafters. Our work includes: Structural engineering calculations Engineering shop drawings Miami-Dade NOAs and Florida Product Approvals Window, door, curtain-wall, storefront, railing, and façade systems Laboratory testing coordination Technical reviews and revisions Professional Engineer review, approval, signing, and sealing Proposals, billing, collections, and project-profitability management We need one senior technical leader who will remain accountable for the complete engagement. The selected architect may use their own development team, but one person must be responsible for architecture, communication, security, delivery quality, documentation, deployment, and long-term support. This is not a website, basic CRM, or simple task-management application. It is a complex enterprise operations platform. Primary Objective The platform must manage the complete lifecycle of an engineering project: Client email → Opportunity → Proposal → Authorization → Project setup → Engineering production → Internal checking → Technical lead review → PE review → QA → Issuance → Billing → Collection → Closeout The system must integrate with our existing applications instead of creating another isolated platform. Required Integrations Microsoft Outlook Microsoft Graph SharePoint OneDrive Microsoft Teams Microsoft Entra ID BQE CORE OpenAI or Azure OpenAI Power BI or custom reporting Company-controlled GitHub and cloud environments Core System Requirements 1. AI Email Intelligence The system should connect to authorized Outlook mailboxes and: Read incoming emails and attachments Identify new versus existing projects Match emails to clients and project records Extract client name, project name, scope, deadline, and requested deliverables Detect technical questions Identify missing project information Identify potential additional services or change orders Draft client responses for human approval Create tasks and reminders Organize attachments in the correct SharePoint project folder Maintain a complete audit trail No external email may be sent automatically without human approval. 2. Opportunity and Proposal Management The system should: Create opportunity records Collect structured project-scope information Search similar historical projects Retrieve previous fee and labor information Generate draft proposals Track proposal status Track authorization and deposit status Convert approved proposals into active projects 3. Automatic Project Creation After authorization, the system should automatically create: Master project record BQE project reference SharePoint project folder structure Project workflow Assigned project manager Assigned technical lead Assigned engineers, designers, and drafters Independent checker Responsible Professional Engineer Tasks and milestones Billing milestones Complete audit records 4. Role-Based Command Center The platform should provide separate dashboards for: Managing Principal Chief Operating Officer Project Managers Technical Leads Engineers Designers Drafters Checkers Professional Engineers QA and Document Control Finance personnel Each user must see only the projects, documents, tasks, and financial information authorized for their role. 5. Controlled Engineering Workflow Projects must move through defined stages: 1. Scope approval 2. Input completeness 3. Design-basis approval 4. Engineering production 5. Independent checking 6. Technical lead review 7. Professional Engineer review 8. QA review 9. Final issuance 10. Revision and closeout The system must prevent required stages from being skipped without authorized approval. 6. Remote Technical Team Management The platform should manage: Project assignments Workload and resource capacity Due dates Priorities Estimated hours Actual hours Dependencies Engineering and drafting assignments Checker assignments Review comments Revision status Team production and performance reporting 7. Professional Engineer Review Center The responsible Professional Engineer should have a dedicated review queue containing: Project summary Design criteria Assigned technical team Critical assumptions Calculations Drawings Internal checking status Technical risks Review comments Revision history Final approval status The AI must never independently: Approve engineering Determine final structural acceptability Select final engineering methodology Sign or seal documents Release deliverables Replace professional engineering judgment 8. Document and Revision Control The platform should: Connect to SharePoint document libraries Track file versions and revisions Distinguish working, review, issued, superseded, and archived documents Prevent accidental release of incorrect files Prevent issued documents from being overwritten Record who prepared, reviewed, approved, and issued each document Maintain a complete audit history 9. BQE CORE and Financial Integration The system should retrieve or synchronize: Contract value Approved change orders Budgeted hours Actual hours Labor cost Remote-team cost Invoices Collections Outstanding balances Billing milestones Revenue-split categories Project profitability Applicants should explain how they would address limitations or gaps in the BQE API. 10. Change-Order Detection The AI should compare: Original proposal scope Included revisions Original assumptions New client requests Additional products, sizes, or configurations Revised calculations Revised drawings Rush requests Client-caused redesign Excessive revision cycles The system should flag potential additional services and prepare a draft change order for approval. 11. Private Engineering Knowledge Assistant The platform should securely search approved company records, including: Historical calculations Engineering drawings Product approvals Miami-Dade NOAs Test reports Installation instructions Agency comments Technical emails Standard details Procedures Lessons learned Every AI response must: Cite the source document Link to the original file Respect user permissions Distinguish final documents from drafts Identify superseded information State when the available source material is insufficient Preferred Technical Experience Applicants should have strong experience with: Enterprise SaaS architecture Microsoft Graph Microsoft Outlook integration SharePoint and OneDrive Microsoft Teams Microsoft Entra ID Microsoft Azure .NET 8 Python or FastAPI React or Next.js PostgreSQL or Microsoft SQL Server OpenAI or Azure OpenAI LLM applications AI agents Retrieval-Augmented Generation Vector databases Document-processing pipelines REST APIs Role-based access control Audit logging CI/CD Cloud security Automated backup and recovery Large PDF and technical-document workflows Experience with engineering, architecture, construction, healthcare, legal, finance, or another controlled professional-services environment is preferred. Non-Negotiable Requirements One senior architect must remain accountable for the complete project. All source code must remain in our company-controlled GitHub organization. All cloud resources must be created under our company-controlled accounts. Hammad Muzaffar or his designated company will own all code, databases, workflows, prompts, documentation, models, and intellectual property created for the project. No critical component may depend on a developer’s personal account. Separate development, staging, and production environments are required. Microsoft Entra ID authentication is required. Role-based permissions are required. Multi-factor authentication is required. Complete audit logging is required. Credentials may not be hard-coded. Automated backups and recovery documentation are required. Architecture, API, deployment, and administrator documentation must be delivered. The system must be transferable to another development team. Confidential engineering data may not be reused. Payment will be milestone-based and subject to acceptance testing. NDA and intellectual-property agreements will be required. Proposed Development Phases Phase 0 — Paid Discovery and Architecture Deliverables: Workflow discovery Requirements specification System architecture Data model Security design Integration assessment Wireframes Development roadmap Milestone budget Risk register Phase 1 — Operational MVP Deliverables: Microsoft login Role-based permissions Master project database Outlook email ingestion AI email classification Project matching Attachment handling SharePoint project linking Basic dashboards Task management Audit logging Phase 2 — Engineering Workflow Deliverables: Project templates Engineering review stages Remote-team assignments Capacity management Checker workflow Technical lead review Professional Engineer review center QA and issuance control Revision management Phase 3 — Commercial and Financial Intelligence Deliverables: Proposal generation Change-order detection BQE integration Budget-versus-actual reporting Billing alerts Collection tracking Profitability reporting Revenue-split tracking Phase 4 — Engineering Knowledge AI Deliverables: Secure document indexing RAG knowledge search Historical-project retrieval Source-grounded AI responses Permission-aware results Draft-versus-issued document controls Superseded-document identification Required Application Format Begin your proposal with the exact words: HAMMAD COMMAND CENTER Your proposal must include: 1. Why you are qualified to lead the complete project. 2. Three relevant systems you personally designed or delivered. 3. Links, screenshots, or case studies. 4. Your exact experience with Microsoft Graph, Outlook, SharePoint, and Entra ID. 5. Your experience with AI agents, RAG, and document intelligence. 6. Your recommended system architecture. 7. Your proposed team and each person’s role. 8. Which components you will personally lead or develop. 9. Estimated timeline for each phase. 10. Estimated fixed price or price range for each phase. 11. Maintenance and long-term support options. 12. Technical risks you already identify. 13. Confirmation that all code and infrastructure will be company-controlled. 14. Confirmation that you will complete a paid discovery or pilot before the full engagement. Generic proposals that only repeat the job description will not be reviewed. Screening Questions 1. Describe the most complex AI-enabled enterprise SaaS platform you personally architected. What was your exact role, what integrations were involved, and is it currently in production? 2. Explain how you would securely read Outlook emails and attachments, match them to existing projects, and store the relevant documents in SharePoint. 3. Describe a RAG or document-intelligence system you built. How did you manage source citations, permissions, outdated information, and hallucinations? 4. How would you architect the system so BQE remains the financial source of truth, SharePoint remains the document source of truth, and the Hammad Engineering Command Center becomes the operational source of truth? 5. What would you include in a two-to-four-week paid discovery and prototype phase? 6. Which components would you personally develop or supervise, and which components would be completed by your team? 7. Confirm that all code will remain in our GitHub organization and all cloud resources will remain under our company account. 8. Provide separate timeline and price estimates for Phases 0, 1, 2, 3, and 4. Skills Artificial Intelligence Software Architecture SaaS Microsoft Azure Microsoft Graph OpenAI API Large Language Model Retrieval-Augmented Generation API Integr