Insights
Plan your website, app or software project with fewer unknowns
You may know the business problem but still be unsure what to build, which features belong in the first version or what information a development team needs. This guide explains the decisions that shape the scope, timeline and cost of a digital product.
Start with the problem, not a technical specification
Describe what is happening in the business today, who encounters the problem and what they need to accomplish. You might be replacing spreadsheets, modernising an existing product, introducing online ordering or turning an idea into an initial release. You do not need to choose the architecture, integrations or every feature before starting a conversation. If you are not sure about any of those details, say so.
Match the project type to the result you need
The right format depends on the users, the task and how the product will be managed. These are distinct types of work, although a project may combine them after its scope is defined.
- Website development For a business that needs a new or updated online presence, the work can cover responsive business websites, landing pages, corporate websites or custom web platforms. The resulting product is a website or web platform built around the agreed pages and functions.
- Mobile app development For a business or startup that needs a product people can use on mobile devices, the work covers iOS and Android applications. The resulting product is a mobile application with the functions established during scoping.
- SaaS product development For an organisation building an online software product, the work can include user applications, administration panels, dashboards, subscriptions and backend systems. The resulting product is a SaaS platform made up of the components selected for that project.
- Custom software development For a business relying on manual processes, spreadsheets or disconnected tools, the work is shaped around its particular workflow and operational requirements. The resulting product is a custom system for managing the agreed activities and information.
- MVP development For a founder or business testing a new product idea, the work concentrates on the first useful version instead of every possible feature. The resulting product is an MVP that can be introduced to real users and used to inform later development.
What to define before asking for a cost or timeline
A useful estimate depends on what is being built and what the product must do. You can begin with partial answers; uncertainty should be identified during discovery rather than hidden behind assumptions.
-
The business problem
Explain the current process, what is difficult about it and what you want people to be able to do differently.
-
The people who will use it
Identify the customers, employees, administrators or other users involved and the main task each group needs to complete.
-
The first release
Separate the functions needed at launch from ideas that can wait. This keeps the initial scope tied to a clear purpose.
-
Product parts and integrations
Note whether you expect a website, mobile app, administration panel, backend or connections to other services. If you are not sure which parts are necessary, describe the workflow instead.
-
Existing material and practical constraints
Share any current website or software, reference examples, preferred launch date and approximate budget if available. These details help test whether the proposed scope fits the situation.
A complete project still needs clear inclusion boundaries
A website, mobile app, administration panel, backend, hosting, payment integration, maintenance and future updates are not automatically one package. The proposal should identify which product parts and features are included, which are optional, the expected timeline and price, the deliverables and the project terms. This is where assumptions about deployment, support and later changes should be resolved.
How an idea becomes a defined project
-
01
Enquiry review
The initial enquiry introduces the business, idea, requirements and current challenges.
-
02
Clarification and discovery
A direct response and discovery call are used to discuss the product, target users, features, integrations, preferred timeline and expected outcome.
-
03
Recommended approach and scope
The proposed solution defines what the project will include before an estimate is prepared.
-
04
Estimate and proposal
The proposal sets out the expected timeline, pricing, deliverables and project terms for review.
-
05
Development and review
After approval and kickoff, progress updates allow the customer to review the product during development.
-
06
Testing, launch and support
The product is tested, final improvements are made and deployment follows. The applicable post-launch support should be clear in the project terms.
Where AI-assisted development fits
AI-assisted workflows can support development, but they do not remove the need to understand the requirements or define the scope. My Faces Production combines these workflows with developer review, testing and engineering oversight. The relevant question is not whether AI is used, but how the finished product is reviewed and prepared for its agreed purpose.
Common planning questions
How much will the project cost?
No universal price is supplied. Cost is estimated after the business problem, product type, main features, integrations and required product parts have been clarified.
How long will development take?
No standard timeline is supplied. The expected timeline is included in the proposal after the scope and preferred launch date have been discussed.
Can an existing product be changed or rebuilt?
Software customisation and enhancement are supported. Share the existing website, app or software and explain what needs to change so the work can be scoped.
Do I need to know every feature before making an enquiry?
No. You can start with the idea, current problem and people who will use the product. Mark uncertain details as “not sure” so they can be explored during discovery.
You can begin with the problem you need to solve
Share your business idea, current process or existing product. You can include examples, a preferred timeline and an approximate budget if you have them, but you do not need to arrive with a finished feature list or technical specification.