Founder-led · Regina, Saskatchewan

Research-informed software.
Better-supported decisions.

Prairie Simple Software brings research, business records and repeatable workflows into practical applications for running your business.

Keep the evidence behind a decision close to the work it affects. Where appropriate, we integrate selected WONDER tools for numerical comparison, evaluation and traceable decision support.

For first-time entrepreneurs and small-business owners.
No technical background needed to start the conversation.

What we can build together

Less scattered work.
More useful information.

Start with the problem. Sometimes the right answer is an existing product or a well-designed spreadsheet. When custom software fits, the scope stays clear.

01 / Understand

Evidence you can
come back to

Organize research and reviewed evidence. Keep each source, assumption and open question attached to the decision it informs, with the review and its reasons retained.

For example: compare supplier quotes without losing units, expiry dates or missing delivery costs.

02 / Operate

Records and scenarios,
clearly separated

Bring recurring tasks and operating records into one workflow. Keep deterministic costing separate from conditional comparisons, with assumptions, limitations and evaluation evidence visible.

For example: compare launch options under stated uncertainty, then record a human decision without turning projected profit into actual sales.

03 / Get comfortable

A guided start.
A defined way forward.

Plan owner onboarding, authorized team access and useful documentation. Agree hosting, maintenance, support and optional integrations separately.

These are scoped services and examples, not a catalogue of completed client projects.

A practical example

Healthy Energy Sask

See the software in practice.

Healthy Energy Sask is a working software application developed around a proposed Saskatchewan business for a business-class project.

It is persistent software with saved records and histories, not a disposable demo. The existing private application is live; the proposed beverage business is not presented as commercially operating or as paid-customer validation.

Aaron directs the design and integration, using AI-assisted development and selected WONDER components. People review the evidence and make the decisions.

Owner-access upgrade ·
The owner-onboarding and invitation upgrade has passed local and hosted automated tests (continuous integration). It has not yet been deployed or accepted by a customer.

Read the documented case study

From a source to a decision

  1. Capture a source

    Save research or quote evidence with its identity and date.

  2. Review the evidence

    Check units, expiry and missing costs. Record the human review; optional AI assistance cannot approve evidence.

  3. Update business records

    Record inventory, sales and expenses. Deterministic costing uses the entered records.

  4. Inspect a comparison

    Read retained results under stated assumptions. New numerical runs require an explicit local action; refreshing a page never runs one.

  5. Record the decision

    Review and save a decision in the local comparison workflow. Retain the inputs, result and reasons; hosted users can read the saved history.

Capabilities, evidence and limits

Saved evidence, operating records and decision history are demonstrated application capabilities. New numerical comparisons and their admission remain local-only. Hosting, onboarding and optional integrations are separately scoped services.

The dated upgrade status above concerns automated tests, including cloud-hosted CI. It does not prove real Auth0 login, production migration, instructor access or customer-operated acceptance. Existing sign-in does not make the new invitation flow live.

The public portfolio preserves its earlier evidence cutoff. This private app is not an anonymous public demo; viewing this website or downloading files starts no AI job or simulation.

No software result here establishes food safety, health efficacy, regulatory approval, customer demand or profitability. Conditional scenarios are not observed sales or actual profit.

How delivery works

A clear scope.
A usable handover.

We agree what a successful result looks like before treating a project as finished.

  1. 01

    Discover

    Walk through the work, the people and the problem.

  2. 02

    Agree

    Set scope, responsibilities and acceptance criteria.

  3. 03

    Review

    Try a prototype and correct what doesn’t fit.

  4. 04

    Build & test

    Check the real workflow, including failure and recovery.

  5. 05

    Get started

    Guide the owner through access, first use and documents.

  6. 06

    Plan ongoing care

    Agree hosting, maintenance and support separately.

What your handover should include

A working HTTPS address, individual owner access, guided first use, relevant documents and a tested operating workflow. We define user management, data export, support and recovery responsibilities in the project scope.

Ordinarily, you use a browser—not an installation ZIP. Optional home-screen installation does not, by itself, provide offline or native-app capabilities.

Behind the work

A toolkit for asking
better questions.

PSS is the founder-led service business that researches, builds and supports tailored applications. WONDER is the broader modular research and decision-support ecosystem we use selectively. Entrepreneurial software is one application, not its entire purpose.

Core

Evidence, structured judgments and records that explain a decision.

Implemented interfaces

Monte Carlo

Reproducible numerical comparisons under explicitly defined assumptions.

Implemented numerical toolkit

Models

Candidate models, bounded parameter estimation and retained learning records.

Implemented tools; bounded experiments

Lab

Synthetic environments for trying methods before relying on them.

Development and research environments

Evals

Tests and evaluation records for checking specific claims.

Evaluation tools; scoped studies

Engineering

A local software-repair workbench with review and execution controls.

Local application

Financial

Quantitative methods and an authenticated decision workspace.

Application and research library

These are ecosystem capabilities, not features included in every PSS application.

Bounded learning experiments are not autonomous production learning. Further integrations and future uses need their own scope, evaluation and acceptance; implementation alone is not universal validation.

Public review edition

Explore the portfolio
and system specification

25 October 2026 · Evidence cutoff: 14:30 UTC

A dated technical snapshot, not a live service-status report. Later tests do not change this edition. No source-code access is granted by these downloads.

Before we start

Practical questions.
Plain answers.

Projects are quoted from scope, complexity, integrations, data migration, testing, onboarding and support needs. We separate the build from ongoing costs.

Terms below describe what must be agreed. They are not a published price list, service-level guarantee or blanket transfer of intellectual property.

Do I install anything? What happens at first login?

A typical web app opens at an HTTPS address in your browser. The agreed handover includes individual owner access or a secure invitation, guided first use and relevant documentation. The exact sign-in and acceptance process is tested for your project.

Can partners work in the same business?

Team access can be included in the scope, with individual accounts and agreed permissions, rather than shared passwords.

Healthy Energy update ·
The owner-onboarding and invitation upgrade has passed local and hosted automated tests (continuous integration). It has not yet been deployed or accepted by a customer. This concerns the new upgrade, not the existing live application. CI does not establish real sign-in or customer acceptance.

Who owns the data and customer-specific code?

Data rights, customer-specific code ownership and any handover rights must be agreed in writing before development. Reusable PSS components and third-party software may remain subject to their own licences. An application delivery does not automatically transfer the entire WONDER ecosystem.

Who pays for hosting, email and AI?

The quote separates one-time build/setup, recurring hosting/support and variable third-party usage. It identifies who holds each account, who pays and what limits apply. AI is optional where the workflow permits it; unlimited usage is not promised.

What support is included—and what is extra?

The agreement defines onboarding, maintenance, covered fixes, contact methods and any response targets. New features, integrations or changes outside that scope are agreed separately. A response target is not a guaranteed resolution time. This is founder-led work, not a staffed 24/7 service.

Can I export my data or leave the service?

Export formats, access, retention, transition help and any exit costs must be specified and tested for your application. We agree the handover and deletion responsibilities rather than assume every deployment has the same policy.

What happens during an outage or if Aaron is unavailable?

The delivery agreement needs named account responsibilities, recovery instructions, backup and key custody, and an availability/continuity plan appropriate to the project. These arrangements must be tested. Neither this website nor a successful local restore establishes production backup protection or guaranteed uptime.

Founder-led, from the Prairies

Start with the work
you want to make easier.

I’m Aaron Moyer, the founder and developer behind Prairie Simple Software and WONDER, based in Regina, Saskatchewan. I direct the research, architecture and development, using AI-assisted tools alongside conventional software engineering.

Bring a workflow, a recurring frustration or a decision you need to understand. We can establish whether a small tool, an existing product or a tailored application fits.

Discuss your project

prairiesimple@proton.me

Describe the workflow and what you would like to improve. Scope and terms are agreed before work begins.

A short description is enough to start. Don’t send passwords, payment details, private customer records or sensitive business documents.

How this site handles information