Custom software development company for Alberta

Start with the work you need to support. An existing product is often a good fit for standard tasks such as accounting, payroll or email. It gives you a defined set of features, while a custom system gives you more control over a process that sets your business apart or falls into the gaps between your existing tools.

A hybrid approach is also an option. You keep a product that already handles standard work and build the missing workflow around it, connected through its API. That limits the custom work, although the connection still needs to be considered as part of the project.

Your choice affects what you need to maintain and how much freedom you have to shape the workflow. We help you assess where custom software has a useful role and will tell you if an existing product fits your needs better. Bring the problems you want to solve, as well as the tools your team already uses.

If your software collects personal information, privacy requirements affect what it records and who can access it. Alberta has its own private-sector privacy law, while federal rules also apply to commercial activity. We set up logins, permissions and audit trails around the information your team needs to handle, with the relevant privacy requirements considered in the scope.

Sales workflows also need the right tax settings. The GST or HST rate depends on the place of supply, including where goods are delivered. We set up the sales and invoice rules around the places your business supplies, including the applicable GST or HST rates.

Bring the material your team uses today and the people who can explain it.

• Sample spreadsheets, forms, templates and records, with notes on the columns people rely on.
• A list of users and what each person needs to see, change or keep private.
• Problems ranked by their cost to the business, such as lost hours, errors or late jobs.
• A named decision maker and a staff member who will test, give feedback and help colleagues adopt the system.
• An outline of who performs each step, which documents and approvals they use, and where work waits.

• !

  Copying a spreadsheet screen for screen

  Fix the process first, then build the simplest system that supports it.

• !

  Putting every request into the first version

  Focus on the biggest bottleneck so the team can use the result to shape what comes next.

• !

  Leaving permissions until late

  Define roles while screens are being designed to reduce rework and avoid showing data to the wrong people.

• !

  Leaving the project without an internal owner

  Name someone who can answer questions, organise testing and help the team adopt the system.