WJP Engineering
Custom engineering software
I build purpose-fit tools that reduce repetitive work, improve consistency, and make engineering output easier to review.
This is a good fit when your team repeats the same checks every week, relies on a growing spreadsheet ecosystem, or needs standardized output for QA/QC and review.
What I build
Lightweight internal tools, calculation automation, or workflow apps that help a team deliver faster without sacrificing quality.
Calculation automation
Reduce manual spreadsheets by turning repeatable checks into consistent, testable computation.
Report generation
Automatically generate clear, standardized reports and calculation packages.
Workflow tools
Simple web apps that track inputs, assumptions, and outputs so your process is repeatable and auditable.
Engineering UX
Interfaces that make it hard to enter bad data and easy to review results.
Example use cases
The exact solution depends on your workflow, but common outcomes look like this:
Standardized calculation packages
Enter inputs once, generate consistent reports with assumptions, units, and checks laid out clearly.
Input validation + QA/QC
Guardrails that prevent common input mistakes and make reviews faster.
Workflow automation
Reduce copy/paste and manual formatting by connecting steps into a repeatable pipeline.
Internal tools for teams
Simple web apps that centralize assumptions and outputs so the process is easier to audit.
How projects run
1. Define
Short discovery to capture requirements, edge cases, and what “done” means.
2. Build
Incremental delivery with review checkpoints—so the tool matches how you actually work.
3. Support
Handover, documentation, and updates as your workflow evolves.
When custom software is a good fit
These are the patterns that usually produce the best return: clear inputs, repeatable checks, and output that benefits from standardization.
Best fit when
- Calculations are repeatable with clear inputs and outputs
- You need consistent reporting and review-ready packages
- Workflows benefit from guardrails and built-in QA/QC
We align early
- Which edge cases and exceptions must be supported
- How results will be validated and reviewed
- Deployment constraints (internal, cloud, offline)
FAQs
Do you take small projects?
Yes—many tools start small. A focused first version can prove value quickly and expand over time.
How do you validate results?
Validation is part of the definition phase: known examples, spot checks, and agreed acceptance criteria.
Start a project
Send a short note with what you’re trying to automate, any constraints (tools, platforms, timelines), and what output you need.
Email: brian@wjpeng.ca