Technical Product Consultant / Application Product Auditor — B2B CRM & Operations Platform

Technical Product Consultant / Application Product Auditor — B2B CRM & Operations Platform Engagement: Hourly / Ongoing Work Type: Remote Reporting: Directly to Founder / Managing Director Development Responsibility: None initially AI Usage: Not permitted for this engagement About the Project We operate Suits Workspaces, a managed office and commercial workspace business in India. Over time, we have developed a substantial internal web application for managing different parts of our business, including: • CRM and lead management • Sales pipeline • Client requirements • Proposals • Properties and inventory • Brokers • Landlords • Tenants • Vendors • Projects • Work orders • Communications • Automation • Finance operations • Analytics • Administration and permissions The application is already operational and continues to evolve. We are now looking for an experienced Technical Product Consultant / Application Product Auditor who can independently evaluate the existing platform and help determine how the product should evolve. This is not primarily a software development role. We need someone who can understand what has already been built, identify what works and what does not, study our actual business workflows, and create a structured roadmap for improving the application. Primary Objective Your responsibility will be to answer: “Given what exists today, how should this application evolve into a scalable operating platform for Suits Workspaces?” You will report directly to the Managing Director. You will independently audit the application and recommend: • what should be improved • what should be redesigned • what should be simplified • what should be removed • what is missing • what should be built next • what should NOT be built • how individual modules should interact • how the platform should scale with the business Development will be handled separately. Current Product Priority Our immediate product priorities are: 1. CRM & Lead Management We want significantly stronger control over: • lead capture • lead qualification • lead ownership • lead stages • follow-ups • stale leads • lead scoring • activity history • sales accountability • conversion tracking 2. Lead Closure The platform should help the sales team move a requirement through: Lead → Requirement → Property Shortlisting → Site Visit → Proposal → Negotiation → Closure We want you to audit where this workflow currently breaks down and recommend improvements. 3. Task Management & Command Center Management needs a strong operational command center showing: • today's priorities • overdue tasks • pending follow-ups • stale leads • site visits • proposals awaiting action • leads approaching closure • team accountability • bottlenecks • management interventions required 4. Property & Inventory Intelligence The application manages office properties and inventory. We need to determine how effectively inventory connects with: • requirements • CRM • proposals • site visits • website listings • marketing • brokers • landlords • availability 5. Operations The platform also supports post-sales operational workflows involving tenants, projects, vendors, work orders and related business processes. These should eventually form a coherent operating system rather than independent modules. Accounting Is NOT the Current Priority We already use Zoho Books for accounting and intend to continue using it. We do not want to turn our internal application into another full accounting system. The application should primarily provide operational financial information and eventually integrate relevant data with Zoho Books through APIs. Part of your role will be preventing unnecessary product expansion when an established external system should remain the system of record. Your Responsibilities Application Audit Review the existing application comprehensively. Understand: • frontend architecture • backend/data architecture • database structure • modules • navigation • permissions • user roles • workflows • integrations • dashboards • reports • automation • existing technical/product debt You do not need to rewrite the application. You need sufficient technical understanding to evaluate whether its architecture supports the intended product. Workflow Audit Understand how Suits Workspaces actually operates. Map important workflows such as: Lead → Requirement → Site Visit → Proposal → Closure → Tenant → Operations Identify: • duplicate workflows • unnecessary steps • missing steps • disconnected modules • poor UX • missing automation • missing management controls • data inconsistencies • opportunities for simplification Product Roadmap Create and continuously maintain a prioritized product roadmap. Every recommendation should be classified approximately as: • Critical Bug • UX Improvement • Workflow Improvement • Technical Debt • New Feature • Automation • Integration • Reporting / Analytics • Security / Permissions • Performance • Future / Optional Recommendations should also be prioritized by: P0 — Critical P1 — High Priority P2 — Important P3 — Future Feature Scoping For approved features, prepare implementation-ready specifications for our development team. A feature specification should define: • business problem • users affected • desired workflow • user stories • screens affected • required data • permissions • edge cases • acceptance criteria • dependencies • expected business outcome The development team should be able to execute the feature without having to reinterpret the business requirement. UX Audit Evaluate whether the application is intuitive for actual business users. We particularly want improvements in: • navigation • information hierarchy • dashboards • forms • tables • search • filtering • empty states • error states • workflows • mobile usability • consistency between modules Scalability Planning We expect the business to expand across locations and cities. The application architecture should eventually support: • multiple cities • multiple properties • larger inventory • larger sales teams • brokers • landlords • enterprise clients • operational teams • marketing attribution • management reporting You should identify architectural or product decisions today that could create scaling problems later. Important: No AI Usage This engagement specifically requires independent human analysis. Do not use ChatGPT, Claude, Gemini, Copilot, or other generative AI tools to perform the application audit, generate recommendations, prepare reports, or create product specifications for this engagement. We are specifically hiring for your: • experience • judgment • analytical ability • product thinking • technical understanding • business understanding Please apply only if you are comfortable working under this requirement. Ideal Background We are particularly interested in candidates with experience in one or more of: • Technical Product Management • B2B SaaS • CRM platforms • ERP / business applications • PropTech • Sales automation • Workflow management systems • Internal business platforms • Enterprise software Experience with products such as Salesforce, HubSpot, Zoho, Monday.com, ClickUp, Odoo, ERPNext or similar platforms is useful because we expect you to understand established workflow patterns. Technical Understanding You do not need to be the primary developer. However, you should be technically comfortable reviewing applications built using technologies such as: • React • TypeScript • Supabase • PostgreSQL • REST APIs • GitHub • Netlify • role-based access control • database migrations • third-party integrations You should be capable of discussing architecture intelligently with developers. Deliverables Initial engagement should produce: 1. Existing Application Audit 2. Module Map 3. Current Workflow Map 4. UX Audit 5. Architecture / Scalability Observations 6. Technical Debt Register 7. Feature Gap Analysis 8. CRM & Lead Closure Audit 9. Command Center / Task Management Recommendations 10. Prioritized Product Backlog 11. 3-Month Product Roadmap 12. 6-Month Product Roadmap 13. 12-Month Product Direction 14. Recommended features we should NOT build 15. Implementation specifications for approved features After the initial audit, this can become an ongoing hourly product-consulting engagement. Working Relationship You will report directly to the Managing Director. You will not manage our employees initially. You will work independently, review the platform, ask questions when necessary, and present recommendations directly to management. We expect someone who can challenge requirements rather than simply agree with them. If a requested feature does not make business or product sense, we expect you to explain why and recommend a better solution. Engagement Model This is an hourly Upwork contract. We would initially prefer a controlled audit engagement and then expand it into an ongoing relationship if the work is strong. Please provide: • your hourly rate • your availability per week • your timezone • relevant SaaS/CRM/ERP products you have worked on • examples of products you have audited or planned • your experience preparing product roadmaps and PRDs • your technical background • your experience working directly with founders/management Application Questions Please answer all of the following: 1. You inherit an existing B2B application containing CRM, properties, proposals, tenants, vendors, projects, finance and automation modules. What would you audit during your first two weeks? 2. How would you determine whether an existing feature should be improved, rebuilt, removed or left unchanged? 3. How would you audit a CRM specifically for improving lead closure? 4. Give an example where you recommended NOT building a feature requested by management. 5. How do you convert a business problem into a specification that developers can implement without ambiguity? 6. What would you expect to deliver after your first 40 hours working on this project? 7. Are you comfortable completing this engagement without using generative AI tools? Applications containing generic agency pitches or proposals that do not answer these questions will not be shortlisted. Who We Are Looking For We are looking for a product thinker with technical depth, not simply another developer. The right person should be able to look at an existing application and tell management: “This is what you have, this is where the product is weak, this is what users actually need, this is what should be built next, this is what should not be built, and this is how we should evolve the platform over the next 12 months.” If that describes the type of work you do, we would like to hear from you.