MVPYGet in touch

    Schedule B.2 · Custom SaaS Development

    Custom SaaS development, built to a written scope.

    Subscription software built around your workflows: user accounts, roles and permissions, subscription billing, dashboards and reporting, and the backend, APIs and integrations behind them.

    The scope, price, milestones and timeline are agreed before the build starts. You see progress on a staging version throughout, and at handover your team receives the source code, documentation and deployment access to carry on.

    Discuss your projectQuestions

    Terms. Custom SaaS Development

    Agreed before the build

    For
    For teams building subscription software, dashboards, user systems and business workflows.
    Typically
    • Accounts, roles and permissions
    • Subscription billing
    • Dashboards and reporting
    • Backend, APIs and integrations
    • 2 weeks of post-launch support
    Price
    Projects from $5,000, fixed before development begins.
    Process
    Discovery, written scope, proposal, build, launch and handover: the same six steps as every engagement.

    This fits when

    1. Whereasyou are building a subscription product, a dashboard or a business platform;
    2. Whereasbilling, user management and reporting have to work properly from launch;
    3. Whereasyour team wants to own and extend the code afterwards.

    Look elsewhere when

    1. Whereasyou need ongoing engineering capacity with no defined scope: that is a hire, not an engagement;
    2. Whereasthe product is still an idea with no agreed first workflow: a focused MVP is the better start.

    Questions. Asked before signing

    How much does a project cost?

    Projects start at $5,000.

    The final price depends on the product's complexity, workflows, integrations, technical requirements and delivery timeline. You get a scoped proposal with a fixed price before development begins.

    What technologies do you use?

    Mostly Next.js, React and TypeScript on the web, Node.js or Django on the backend, PostgreSQL or MongoDB for data, and React Native with Expo for mobile apps.

    The stack for your project is agreed in the proposal. Not every project uses the same one.

    How are payments structured?

    Payments are tied to agreed project milestones. The schedule is set out in the contract before work begins.

    Can I see progress during development?

    Yes. You get regular progress updates, demos of working features and a staging version to review.

    Repository access during the build is agreed in the contract.

    Can my own team take over?

    Yes. Handover includes the source code, documentation and deployment access, so your team or another developer can carry on from where the build ends.

    What happens after launch?

    Every build includes 2 weeks of post-launch support to fix anything that doesn't meet the agreed acceptance criteria.

    After that, ongoing maintenance, new features and improvements are scoped separately.

    All questions

    Have a product to build?

    I read every enquiry myself and reply within one business day.

    Discuss your project