Services · Engineering

    Software product development services for SaaS and platforms that have to scale

    Software product development is building software you sell to many customers: one codebase, a roadmap, releases that never stop, and customers who each want something slightly different. AMT engineers products end to end, from first release through multi-tenant scale, and stays to maintain them. Some of our product engagements have run for more than six years.

    Schedule Technical Discovery

    Your first conversation will be with a senior technical partner, not a salesperson.

    A product is not a project

    The difference shapes every engineering decision, so it is worth being clear.

    A product is not a project
    ProjectProduct
    CustomersOneMany, with different needs
    Ends whenIt is deliveredIt is retired
    Success measureDelivered to scopeCustomers renew and pay
    ArchitectureFits one organisationIsolates tenants, scales per customer
    ReleasesA few big onesContinuous
    Biggest riskScopeEvery customer's request becoming the roadmap

    If you are building for one organisation, see custom software development instead.

    What AMT owns at each stage

    What AMT owns at each stage
    StageThe questionWhat AMT deliversMove on when
    1. DiscoveryWho pays, for what, and what must version one do?Written scope, architecture note, risks, estimate rangeYou sign the scope
    2. First releaseWill customers use it?A working product with the smallest set of features that proves itReal customers use it weekly
    3. Product-market fitWhat do customers keep asking for?Fast iterations, analytics, feedback loopsRequests repeat across customers
    4. Multi-tenant scaleCan it serve many customers safely?Tenant isolation, per-tenant configuration, role-based access, CI/CDNew customers onboard without engineering
    5. Long-term productCan it keep evolving for years?Maintenance, upgrades, new modules, security updatesIt does not end. That is the point

    Stage 2 in detail, including what to have ready before you brief anyone, is on Build your product.

    Five signs you need a product engineering partner, not a development shop

    1. Your second or third customer needs something the first did not, and the code is fighting you.
    2. Onboarding a new customer needs a developer.
    3. You release less often than you want because every release is risky.
    4. One customer's data could, in theory, be seen by another.
    5. Nobody on the team can say what it costs to serve one customer.

    Proof

    Proof
    Case studyWhat AMT did
    Multi-tenant last-mile delivery SaaSFull product lifecycle for a German EV maker: white-label consumer app, rider app, operator dashboard, Bluetooth smart locks
    Cloud fleet management platformMulti-tenant platform on 12+ Spring Boot microservices, Kafka and AWS, from requirements to CI/CD and support
    Patient analytics platformSix years of product development and maintenance for a platform used by hospitals and clinics in India
    Rental relationship platformCloud platform with DocuSign leases, digital inspections and a housing organisation portal for a US public benefit company
    Enterprise GRC platformConfigurable, multi-organisation GRC product owned end to end

    What we build products with

    What we build products with
    LayerTechnologies
    Front endAngular, React, Next.js, Vue
    Back endJava and Spring Boot, Node.js, NestJS, .NET, Python
    DataPostgreSQL, MySQL, SQL Server, MongoDB, Firestore, Redis, Elasticsearch
    MessagingApache Kafka
    IdentityKeycloak, OAuth 2.0, JWT
    Cloud and DevOpsAWS, Docker, Kubernetes, Jenkins, SonarQube
    MobileSwift, Kotlin

    Adding AI to your product? See AI product engineering.

    How product engagements are set up

    Most products start with a discovery sprint, then move to a dedicated development team that owns the product or a module, usually for six months or longer. Every engagement moves through the five delivery gates on How we work. Models and who carries which risk are on Engagement models.

    What drives product development cost

    We quote after discovery.

    What drives product development cost
    DriverLower effortHigher effort
    TenancySingle customerMany tenants, isolated data and configuration
    AppsWeb onlyWeb plus native iOS and Android
    IntegrationsFewPayments, e-signature, hardware, third-party APIs
    Release paceMonthlySeveral times a week, with CI/CD and quality gates
    RegulationLightHealth, financial or personal data rules

    FAQ

    What are software product development services?

    Engineering a software product that many customers use: discovery, architecture, building the first release, scaling to many tenants, continuous releases and long-term maintenance.

    What is the difference between product engineering and custom software development?

    Custom software is built for one organisation. Product engineering builds one product for many customers, so it has to handle tenant isolation, configuration per customer, continuous releases and a long-term roadmap.

    Can you build a SaaS product with multi-tenancy?

    Yes. Several AMT products are multi-tenant, including a last-mile delivery SaaS, a fleet management platform on 12+ microservices, and a multi-organisation GRC platform.

    Do you maintain the product after launch?

    Yes. AMT has developed and maintained one patient analytics platform for six years, and supported a humanitarian NGO's platform under SLA for more than six years.

    How do you charge for product development?

    Usually a discovery sprint first, then a dedicated team on a monthly fee, or fixed scope for well-defined phases. We quote after technical discovery.

    Tell us what your product does, who pays for it, and where it is today.

    Starting from zero? →