Software & Cloud Development

Software development

Promatics designs, builds and supports software: business applications, customer portals, mobile apps and the cloud services behind them. We work as your delivery team or alongside your internal IT, and we plan for security, integration and support from the first conversation.

Who this service is for

A good fit if

  • You need software that supports a core process, and packaged products do not fit without heavy workarounds.
  • Your internal IT team is stretched and needs a delivery team for a defined project or an ongoing product.
  • The new software must connect to systems you already run, such as Microsoft 365, an ERP or a CRM.
  • You want security, privacy and accessibility treated as requirements, not added at the end.
  • You want to own the code, the cloud accounts and the documentation when the work is done.

Another approach may suit you better if

  • A packaged product already does what you need with light configuration. We will say so and help you set it up instead.
  • You need a small brochure website or a minor change to an existing template site.
  • You want a fixed price and date before any discovery on a project whose scope is not yet known.

What this service is

Software development at Promatics covers the full life of an application: understanding the problem, designing how people will use it, building and testing it, deploying it to a secure environment and supporting it afterwards. We build business applications, customer and partner portals, web and mobile apps, integrations, and the cloud infrastructure they run on.

Because Promatics is also a managed IT, cybersecurity and ERP provider, we treat software as part of your wider environment. A new application has to sign users in through your identity platform, follow your security policies, exchange data with your ERP or CRM, and be supportable by whoever runs your IT. We design for all of that from the start, rather than discovering it at go-live.

What we build

Technologies we work with

We choose technology for maintainability and fit, not novelty. Typical choices include TypeScript and JavaScript with React and Node.js; Python, .NET and Java on the server; Swift and Kotlin for native mobile; Flutter or React Native for cross-platform apps; PostgreSQL and other relational databases; and containers or serverless services on AWS, Microsoft Azure or Google Cloud. Sign-in usually runs through Microsoft Entra ID, Google or another OpenID Connect or SAML provider, so staff use the accounts they already have.

We keep up with new tools and adopt them when they solve a real problem for you, and we tailor solutions to sector-specific rules and workflows in areas such as healthcare, finance and manufacturing.

What you gain

  • Focus on your core business. Your people run the organization while we handle design, engineering and delivery.
  • Productivity and efficiency. Software that fits the way work is actually done removes manual steps, duplicate entry and workarounds.
  • Predictable budgeting. Work is scoped in phases with estimates in CAD, and ongoing support can be arranged on a predictable monthly basis under a written agreement, instead of surprise invoices when something breaks.
  • Protection for your business and data. Security and privacy are requirements from discovery onward, with attention to PIPEDA and applicable provincial privacy laws. This is general information, not legal advice, and we work with your advisers on specific obligations.
  • Scalability. Architecture and hosting are planned so the software can grow with users, data volumes and new locations.
  • An engagement that fits your size and budget. It can be a single phase for one department or a longer-term product team.

Support after launch

Software needs care after it goes live: security updates, operating system and browser changes, new features and the occasional incident. Managed-service clients can have their applications included in 24/7 monitoring and support alongside their managed IT services and IT help desk, with response targets set in the service agreement. If you are still deciding what to build, IT consulting and advisory can set priorities first, and our network and connectivity services cover the infrastructure your software depends on.

What is included

The exact list is agreed in writing for each project. These are the usual deliverables and the usual boundaries.

Typical deliverables

  • A discovery summary covering goals, users, constraints, systems involved and a prioritized first release.
  • An architecture outline covering hosting, data storage, integrations, authentication and security controls.
  • Working software delivered in short iterations, with a demonstration at the end of each one.
  • Automated tests, peer-reviewed code and a repeatable build and deployment pipeline.
  • Integration with the agreed systems through supported APIs.
  • Security checks during development, including dependency scanning and review against OWASP guidance.
  • Accessibility checks against WCAG 2.2 AA for user-facing screens.
  • Technical documentation, an operations runbook and administrator training.
  • Source code, infrastructure definitions and accounts transferred to your organization.

Not included unless agreed separately

  • Third-party licences, cloud hosting, app store fees and paid APIs, which are billed to you directly with your approval.
  • Hardware and end-user devices.
  • Ongoing support, monitoring and enhancements after handover, unless covered by a separate agreement.
  • Legal, tax or regulatory advice. We implement the requirements your advisers confirm.

What we will need from you

Most delays in this kind of work come from access and decisions, not from the technical build. Knowing these early keeps the project predictable.

  • A product owner on your side who can make decisions and approve releases.
  • Access to the systems the software must connect to, preferably test or sandbox environments.
  • Representative users who can take part in discovery sessions and testing.
  • Existing documentation, data samples and brand assets where they exist.
Delivery

How the work is delivered

Most engagements follow the same path whatever their size. Smaller projects combine stages.

  1. Initial call and discovery

    We start with a call at a time that suits you, then a discovery and consulting session to understand the problem, the users, the systems and the constraints.

    Output: Discovery summary and a written proposal with estimates in CAD.

  2. Design and architecture

    User journeys, wireframes and an architecture outline are agreed before the build begins, so changes stay inexpensive.

    Output: Approved designs and architecture outline.

  3. Iterative build

    Software is built in short iterations with regular demonstrations. You see working features early and can change priorities between iterations.

    Output: Working increments in a test environment.

  4. Testing and release

    Functional, integration, security, accessibility and performance testing, followed by a planned release with a rollback path.

    Output: Test evidence and a production release.

  5. Handover and support

    Documentation, training and transfer of code and accounts. Ongoing support can continue under a written agreement.

    Output: Handover pack and optional support agreement.

Testing and handover

  • Every release passes automated tests and a peer code review before it reaches production.
  • Dependencies are scanned for known vulnerabilities, and each finding is fixed or recorded with a reason.
  • User-facing screens are checked against WCAG 2.2 AA, including keyboard and screen reader use.
  • Deployments are repeatable from the pipeline, with a tested way to roll back.
  • You receive the source code, infrastructure definitions, credentials in your own password vault and a runbook.

What affects the cost

We do not publish package prices. Each estimate is based on an agreed scope, in Canadian dollars, with taxes shown separately. These are the things that move the number most:

  • The number of user roles, screens and business rules.
  • The number and quality of integrations with existing systems.
  • Security, privacy, audit and accessibility requirements.
  • The platforms required (web, iOS, Android) and the devices supported.
  • Data migration from existing systems.
  • The level of support and monitoring needed after launch.

Questions buyers usually ask

Should we build custom software or buy a product?

Buy when a product fits your process with reasonable configuration, because someone else maintains it. Build when the process sets you apart or products force costly workarounds. Often the answer is a product plus integrations or a small custom layer, and discovery is where we make that call with you.

Who owns the code?

You do. The written agreement assigns ownership of the code built for you, and repositories, cloud accounts and app store accounts are set up in your organization's name. Open-source components remain under their own licences, which we list.

Can you work with our internal IT or development team?

Yes. We can deliver a whole project, add developers to your team, or take on a defined part such as the mobile app or the integrations, following your standards and tools.

How do you estimate cost and timelines?

After discovery we provide a written scope with estimates in CAD, broken into phases so you can approve one release at a time. We do not quote a fixed date or price before we understand the scope.

What happens after launch?

You can take over with the documentation we provide, or keep us on under a support agreement for fixes, updates and enhancements. Managed-service clients can have applications covered by 24/7 monitoring and support, with response targets set in the service agreement.

Have software you need built or fixed?

Tell us what the software needs to do, who will use it and which systems it must connect to. We will reply to arrange a discovery conversation before anything is priced.