I'm looking for a rough estimate for building a SaaS.

The product needs to interact with an external product or have a payment service live within it.

Basic stuff like user management, team configuration, creating a dashboard overview, lists and manipulation of business data objects, personal settings, and a administration panel for content management.

The product needs to interact with an external product or have a payment service live within it.

The features I need are more deeply complex in terms quantity and quality; there is some very specific business logic required as well.

There are also complex requirements in terms of hosting, data or security.

I don't need Lifely support with me with it's design capability.

Both disciplines are needed yet I don't need Lifely to support me with product ownership.

I require both developers and designers, as well as someone to guide them: a product owner.

I require a development team, product designers, someone who takes ownership of the product, but also need support at the C-level (e.g. interim CTO or CPO).

My team takes full responsibility over the direction of project. We determine the budgets, define the scope of the milestones, describe the user stories, prepare the backlogs and take responsibility for the goals of the project, we just need some capacity in the production team.

I want the Lifely team to take governance over the agile development and to make sure the sprints are run as smoothly and efficient as possible.

I'm relatively inexperienced in building software and need full support to keep the project on track and on budget. I see my role as a bridge between my company or industry and your internal teams.

I'm a strategic thinker, entrepreneur or relatively inexperienced in digital and want to spend as much time as possible running my company, raising money or selling my SaaS to customers. I need a full department that can take complete ownership.

I have a lot of experience preparing work for design and development teams and will take full responsibility over the product strategy. My internal teams will deliver on requirement engineering, wire-framing, roadmap management, user involvement and the go-to-market strategy.

What we need to build is clear to me, however I can use some help figuring out the technical requirements and user experience.

I primarily need help aligning internal stakeholders and making sure all requirements are signed off on. We do not have user experience and technical know-how within our company. I expect Lifely to define on the goal and strategy of the product and involve users in the process.

I would like your full involvement when it comes to the strategy of the SaaS product. I need help defining the business model of the SaaS and the go-to market strategy. Let's develop the concept together, do extensive user validation and develop a well thought out roadmap.

We want to cater to early adopters or internal (power) users. Let's use reusable components like Bootstrap or Material UI to accelerate to development process. I understand that the UI of my SaaS might be a bit limited to what this design system offers in functionality.

I want users to recognise my brand when using the SaaS. You can still use a component library like Bootstrap or Material UI just as long as use our logo, brand colours and font in the application. I understand that the UI of my SaaS might be a bit limited to what this design system offers in functionality.

I want users to recognise my brand when using the SaaS. We can use Material UI as a foundation, however I want us to build custom features and flows if this benefits the user experience of the product.

Brand experience is vital to the product. I want the soul of my brand to be translated into the UI of the SaaS solution. I understand that we are building a custom front-end experience with a rich and beautiful design.

I want all our energy and budget to be focused on validating assumptions and the businessmodel of the SaaS. I understand that if we want to scale the SaaS we might have to partly build or re-build because of limitations or technical complexities.

I want us to focus on accelerating the proces of building a first version of my SaaS without risking a premature need for a rebuild. Use technology that accelerates the development process yet gives us the freedom to upgrade to a more sustainable technology in the future.

I want it done right without over engineering the product. Let's make something that breeds longevity and quality. We need to take into account that one day my own team of engineers have to take over the codebase, so documentation, standardisation, and end-to-end testing are important to me.

I'm doing a rebuild of an existing product and I need do not need to validate assumptions. I want to go all in on the technical side an use technology that scales almost infinitely. Examples include: a microservice architecture, high availability Kubernetes cluster and an automated end-to-end testing suite.

My product works standalone and does not need integrations with other API's, and it doesn't matter where the platform is hosted.

The first version of the product works stand alone, but please take into account future integrations with well established and documented API's like Zapier, Stripe, Adyen or a modern CRM or ERP.

The SaaS needs to integrate with one or two well known and well documented API's like Zapier, Stripe, Adyen or a modern CRM or ERP. But aIso, it is fine to use products such as UI-Path robots to retrieve and store data in legacy software, large platforms like SAP, or less reliable API's.

The SaaS needs to be integrated into our existing IT infrastructure, and our clients need specific integrations to our product such as Single SignOn and exporting data with API's. We might also need to connect to a service bus, like Kafka or IBM Websphere to exchange data with our existing applications.

The SaaS is not going to be mission critical to my customers, therefore I want the servers to be as lean and inexpensive as possible

The product is important to my clients but not necessary mission critical, therefore I'm not demanding high availability but I'd like at least to agree on response times and estimates within office hours

The SaaS is mission critical to my customers. I don't need 24/7 support but I want to agree on fast incident solving within a day

The SaaS is mission critical to my customers and I want to full uptime guarantees, 24/7 support, zero downtime deployments and instant rollbacks / failover clusters