Process & Quality
Know how your software will be scoped, reviewed and handed over
Before approving a build, you need to know what is included, what you can inspect and what happens after launch. My Faces Production defines the agreed features, responsibilities, costs, review points and handover arrangements before development begins. You can start with a business problem or product idea - you do not need a finished feature list or technical specification.
From an enquiry to an agreed build
-
01
Describe the situation
Share the business problem, idea or existing product you want to improve. If you are unsure what features, integrations or product parts you need, that can be explored during discovery.
-
02
Clarify the requirements
The discussion covers the intended users, important workflows, required product parts, integrations, preferred timing and expected outcome.
-
03
Define the scope
The proposed approach sets out the included deliverables, responsibilities, exclusions, estimated timeline, price and project terms.
-
04
Confirm and begin
Once the proposal is approved, the agreement is finalised and development begins. Progress updates and product reviews give the client opportunities to provide feedback during the build.
-
05
Review before acceptance
The development team reviews the implemented functionality, user flows, interface and responsiveness. Identified issues are corrected and checked again. The client can inspect the agreed features and workflows and report issues under the acceptance terms.
A reviewable example: RestaurantFlow
RestaurantFlow is a My Faces Production-owned product demo, not a customer case study. For its restaurant ordering and billing workflows, the team checks menu and table ordering, order details, billing calculations for configured charges and the interface at different screen sizes.
The public demo also gives a reviewer something concrete to inspect. In a browser observation on 9 October 2026, removing the sample 10% service charge changed the visible draft-bill total from INR 1,486.49 to INR 1,351.35 and set that charge to zero. This demonstrates an interactive interface response; it does not establish accounting accuracy, tax compliance, backend reliability or a customer business result.
Restaurant software · Web
RestaurantFlow
Restaurant Ordering, Billing & Table Management
A restaurant-management demo covering QR table ordering, table sessions, kitchen and administration workflows, configured billing and reports.
What deployment covers when it is included
Deployment work is defined for the individual project. For suitable websites and web applications, this can include reviewing the build configuration and environment settings, deploying to Firebase Hosting or Vercel, configuring included APIs, databases and integrations, and checking that the deployed application loads and its agreed core workflows operate in that environment.
- The client supplies access to the relevant hosting, cloud, domain and third-party accounts.
- Hosting subscriptions, cloud usage and other continuing charges remain the client's responsibility unless the agreement says otherwise.
- The handover can include deployed application links and the setup or deployment instructions listed in the scope.
- Mobile build preparation and store-submission assistance are available only when agreed. The client supplies the store accounts, verification details, listings and required legal or privacy information; publication approval remains with the store.
Agree what changes hands
-
Source and project files
Source code and project files are provided for custom development or when source delivery is part of the agreement. Repository access is arranged as agreed, while third-party components remain subject to their licences.
-
Accounts and access
Where possible, the client retains ownership of domain, hosting, cloud, app-store and other business accounts. My Faces Production can configure the agreed deployment and provide the applicable access and handover instructions.
-
Documentation and guidance
The scope may include setup, deployment, environment and main-feature instructions. API documentation, database or architecture material, training, recordings and administrator manuals are included only when agreed.
-
Final review
The client can inspect the delivered features, report outstanding issues and confirm acceptance according to the project agreement. The scope determines whether agreed corrections happen before or after handover.
Product review is not the same as independent assurance
The standard development review applies to the functionality and workflows agreed for the project. My Faces Production does not claim a universal automated-test coverage level, formal QA certification, independent assessment or written test report.
Independent security audits, penetration testing, third-party compliance assessments and extensive automated testing are not automatic parts of a project. If the product requires any of these, the requirement and the responsible provider need to be agreed before work begins.
What can affect scope, cost and timing
- Hosting, cloud usage, domains, paid APIs, software licences, payment services and app-store fees are separate unless explicitly included.
- Only the features, integrations, workflows and platforms named in the agreed scope are included. Additions require discussion and a separate estimate.
- The client supplies or approves business information, product details, prices, branding, images and legal or privacy materials unless their creation is included.
- Payment-provider verification, app-store review and other external approvals are controlled by the relevant provider.
- Timelines depend on the agreed work, client feedback, access to required accounts and materials, and external approvals.
After launch, different needs have different scopes
-
Defects in delivered functionality
Post-launch support may include correcting defects in the agreed functionality according to the project's support terms.
-
Maintenance and operations
Dependency updates, compatibility work, monitoring, backups, cloud management and continuing deployment support are included only when the agreement identifies them.
-
New work
New features, integrations, design changes and expanded workflows are estimated separately from corrections to the agreed delivery.
-
Support terms
The duration, included tasks or hours, charges and exclusions are set for each project. There is no universal support period, fixed response-time commitment or 24-hour service promise.
Bring the problem, even if the specification is not ready
Explain what you want to launch, replace or improve. My Faces Production can use that discussion to clarify the required product parts, review points, deployment responsibilities, handover and post-launch needs before proposing a scope.