Row Start
Q1. What are we building? Pick what feels closest. Don’t worry if it doesn’t fit perfectly; we’ll refine as we go.
Row End
Row Start
Q2. Which platforms do you want to build for? Where do you imagine people using this?
Q2. Which platforms do you want to build for? Where do you imagine people using this?
Do you already have an existing product? Row End
Row Start
Q3. What do you want help with? Where do you need us in your journey?
Row End
Row Start
Q4. Do you need help with branding? How’s your brand looking right now? Let us know where you stand.
Row End
Row Start
Q5. How would you like this project to be approached? Let’s talk about what “done right” means for you. This step is about matching the approach to your goals and stage.
Q5. How would you like this website to be approached? This helps us match the design, functionality, and execution level to your goals and stage.
Row End
Row Start
Q6. What’s your product catalog size and complexity? How big and complex is your inventory system?
Additional Option: Q6. What best describes where your SaaS product is right now? Where are you on the journey?- A new build, expansion, or improvement?
Q6. What type of CMS are you building? This helps us define the functional domain of your CMS.
Q6. Which industry will this CRM primarily serve? This helps us tailor workflows, data models, and integrations.
Q6. What type of marketplace are you building? This defines your business model and platform structure.
Q6. What type of learning experience are you building? This helps us understand how content is delivered and how interactive the platform needs to be.
Q6. What type of community are you building? This helps us understand the core interaction model and platform architecture.
Q6. What type of membership model are you offering? This helps us understand how access, pricing, and entitlements will be structured.
Q6. What type of bookings will users make? This helps us understand the core booking logic and resource types.
Q6. What type of media content will your platform focus on? This helps us understand content formats and delivery complexity.
Q6. Which industry or domain is this AI platform focused on? This helps us understand regulatory, data sensitivity, and domain-specific complexity.
Q6. What type of on-demand service are you delivering? This helps us understand the core delivery model and operational workflows.
Q6. What type of job platform are you building? This helps us understand your recruitment model and platform focus.
Q6. What is the primary focus of your professional network? This helps define positioning, core value, and product architecture.
Q6. What type of social media platform are you building? This helps define the core social experience and content model.
Q6. What type of communication platform are you building? This helps define the primary use case and system architecture.
Q6. What type of business application are you building? This helps define business goals and overall platform scope.
Q6. What type of website are you building? This helps define the core purpose and structure.
Q6. Who will mainly use this product? This helps us understand user roles and system complexity.
Row End
Row Start
Q7. What payment and checkout features do you need? Choose how your customers will pay and complete purchases.
Q7. What is your primary business model? This will help us structure your user flows, permissions, and overall system logic.
Q7. How complex will your content structure be? This helps estimate data modeling and system design effort.
Q7. How complex will your CRM data structure be? This defines how much engineering is needed behind the interface.
Q7. What type of members and roles will your community include? This helps us design roles, permissions, access levels, and moderation structure.
Q7. What will primarily be listed on your marketplace? This determines listing structure, browsing flow, and data modeling.
Q7. What type of learning experience are you building? This defines authoring tools, permissions, and operational complexity.
Q7. What type of content or benefits will members access? This defines delivery logic and entitlement complexity.
Q7. How will bookings be fulfilled and managed operationally? This helps us understand how services are delivered, who fulfills them, and how complex coordination needs to be.
Q7. How large will your content library be? This affects storage, search, and content management complexity.
Q7. What is the primary role of AI in your platform? This helps us understand how central AI is to the product and how much custom AI work is required.
Q7. What is your delivery business model? This defines marketplace logic and operational ownership.
Q7. What job posting and employer tools are required? This defines employer experience and monetization complexity.
Q7. What profile and identity features are required? This defines data models and profile complexity.
Q7. What content creation features are required? This defines media handling and creator tooling complexity.
Q7. What messaging features are required? This defines real-time systems and message handling complexity.
Q7. What user types and access models are required? This defines authentication, roles, and permission complexity.
Q7. Roughly how many unique page templates will you need? This helps estimate design and development scope.
Q7. What outcome are you hoping to achieve with this product? This helps us understand what success looks like for you.
Row End
Row Start
Q8. What level of inventory and order management do you need? How hands-on do you want to be with stock and orders?
Q8. What type of SaaS platform(s) are you building? Select all that apply. This helps us understand the product’s domain complexity and functional scope.
Q8. How will content be created and managed? This defines workflows, permissions, and operational complexity.
Q8. How will your CRM be used operationally? This helps design workflows and system behavior.
Q8. Do you want to incorporate SaaS-style features into your marketplace? This defines whether your marketplace is also a product platform with tools and workflows.
Q8. How complex will your access and entitlement rules be? This affects gating logic and backend permissions.
Q8. How complex will your course structure be? This affects data modeling, navigation, and learning logic.
Q8. How will content and interactions be structured? This affects data modeling, feeds, and navigation logic.
Q8. What scheduling and availability features do you need? This affects calendar logic and real-time availability.
Q8. What streaming quality and playback features do you need? This impacts encoding, player complexity, and infrastructure cost.
Q8. What type of AI capabilities will you need? This defines model types and system architecture.
Q8. What driver and fleet management features are required? This defines real-time systems and driver app complexity.
Q8. What candidate features and tools do you need? This affects job seeker experience and system complexity.
Q8. How will members connect and network? This affects graph logic and social architecture.
Q8. What social interaction features do you need? This affects engagement systems and real-time logic.
Q8. What video and voice capabilities do you need? This impacts real-time media infrastructure.
Q8. What core workflows will the system support? This defines business logic and operational scope.
Q8. How custom or visually advanced should the design be? This defines the level of design effort.
Row End
Row Start
Q9. Do you need any of these advanced features? Anything that makes the experience smarter or more delightful?
Q9. Who will be using this SaaS? Select all user types who will access your product- this defines roles, permissions, and workflows.
Q9. Which core CMS features must be included? Select the key capabilities your CMS must support.
Q9. Which CRM features must be included? Select all that apply — these directly impact scope, effort, and system complexity.
Q9. Which marketplace features must be included? Select all that apply — these directly impact scope and effort.
Q9. What assessment and progress tracking do you need? This determines evaluation logic and reporting complexity.
Q9. What member interaction features do you need? This determines real-time systems and social feature complexity.
Q9. What subscription and billing features do you need? This determines billing logic, lifecycle management, and revenue complexity.
Q9. What booking management features are required? This defines lifecycle flows and operational tooling.
Q9. What content management and delivery features are required? This defines your media pipeline and operational tooling.
Q9. What level of AI customization is required? This impacts R&D effort, cost, and delivery timelines.
Q9. What customer-facing delivery features do you need? This impacts user experience and real-time updates.
Q9. What recruiter and hiring workflow features are required? This defines ATS depth and collaboration needs.
Q9. What discovery and recommendation features do you need? This defines search, AI, and growth mechanics.
Q9. How will users discover content and connections? This defines feed algorithms and growth mechanics.
Q9. What collaboration and productivity features are required? This defines platform depth beyond messaging.
Q9. What integrations and enterprise systems are required? This impacts architecture and IT involvement.
Q9. What conversion and marketing features are required? This defines the marketing tech stack.
Row End
Row Start
Q10. What shipping and fulfillment features do you need? How will products reach your customers?
Q10. Which core modules will your SaaS definitely need? Select all that apply- What features are non-negotiable?
Q10. Do you need any advanced or technical capabilities? These directly impact architecture, timeline, and cost.
Q10. Do you need integrations or data migration? These significantly affect architecture, cost, and delivery timelines.
Q10. Do you need payments, logistics, or external integrations? These significantly affect technical complexity and cost.
Q10. What learner engagement and community features do you need? This affects real-time systems, moderation, and social architecture.
Q10. What moderation and community management tools are required? This impacts admin tooling, safety, and operational complexity.
Q10. What member engagement and retention features are required? This affects lifecycle flows and CRM-style functionality.
Q10. What payment and pricing structure will you use? This defines billing logic and pricing complexity.
Q10. What monetization model will your platform use? This defines billing logic and access control.
Q10. What data and training requirements do you have? This defines data pipelines, storage, and compliance needs.
Q10. What business and operations tools are required? This defines backend complexity and operational control.
Q10. What monetization or business model will you use? This defines billing logic and revenue flows.
Q10. What professional tools and engagement features are required? This defines platform depth and monetization potential.
Q10. What monetization model will your platform use? This defines revenue logic and platform economics.
Q10. What admin, security, and compliance features are required? This impacts enterprise readiness and architecture.
Q10. What data, security, and compliance requirements apply? This defines governance and enterprise readiness.
Q10. What interactive or functional features are needed? This surfaces product-like complexity.
Row End
Row Start
Q11. Do you need any of the following technical or integration capabilities? Heads up: These requirements significantly affect architecture, timeline, and cost.
Q11. What is the primary goal of your CMS? This helps prioritize design and development focus.
Q11. What level of automation or intelligence do you expect? This defines system sophistication and AI readiness.
Q11. What level of trust, compliance, and moderation do you require? This helps us design safety, control, and governance mechanisms for your platform.
Q11. How will learners access and pay for content? This defines billing logic and access control complexity.
Q11. What access and monetization model will your community use? This defines gating, billing logic, and membership structure.
Q11. Do you need any advanced or technical capabilities? These significantly impact architecture, integrations, and timeline.
Q11. What customer and relationship management features do you need? This affects CRM-style logic and personalization.
Q11. What user personalization and account features do you need? This affects data models, UX logic, and engagement systems.
Q11. How will users interact with AI features? This affects UX complexity and system design.
Q11. Do you need any advanced or technical capabilities? These significantly impact architecture, integrations, and scalability.
Q11. Do you need any advanced or technical capabilities? These significantly impact architecture, compliance, and integrations.
Q11. What monetization model will your platform use? This defines revenue logic and access tiers.
Q11. Do you need any advanced or technical capabilities? These significantly impact architecture, scale, and cost.
Q11. What deployment and scale will your platform support? This defines infrastructure and performance planning.
Q11. What scale and organizational complexity is expected? This impacts system architecture and long-term planning.
Q11. What technical or performance requirements apply? This impacts architecture and timeline.
Row End
Row Start
Q12. How will the platform monetize? This helps us estimate billing logic, fee calculations, and the level of admin controls needed.
Q12. Do you need any advanced or technical capabilities? These significantly impact architecture, integrations, and timeline.
Q12. Do you need any advanced or technical capabilities? These significantly impact architecture, integrations, and scalability.
Q12. Do you need any advanced or technical capabilities? These significantly impact architecture, integrations, and operational complexity.
Q12. Do you need any advanced or technical capabilities? These significantly impact architecture, security, and scalability.
Q12. Do you need any governance, security, or compliance capabilities? These significantly impact architecture, cost, and risk management.
Q12. Do you need any advanced or technical capabilities? These significantly impact architecture, compliance, and scale.
Q12. Do you need any advanced or technical capabilities? These significantly impact architecture, scalability, and delivery effort.
Q12. Do you need any advanced or technical capabilities? These significantly affect scope and delivery effort.
Row End
Row Start
Q13.Help Us Understand Your Vision Better Share anything that will help us personalize your proposal — goals, references, inspiration, or constraints.
Row End
Submit
