01
Searchable historical records
Give people a practical way to find the record they need and understand what it contains.
Existing software + existing data
Make your existing software and data more useful.
Bring business information into a usable application, improve software your team already relies on, or work out a practical next step for a struggling system. We start with what exists and what needs to work better.
Work directly with Brad Conklin, an independent software developer based in Edmonton.
Start with a free fit review.
If I can’t give you a fixed quote yet, the first paid phase is capped at $500 USD.
Pricing and process →
01 / Existing information
Bring existing data online.
Your business may already hold the records people need. The missing part is a practical way for staff or customers to find and use them. I can build interfaces over existing information, with access shaped around the people using it.
02
Documents connected to records
Keep related documents within reach of the information they explain.
03
Staff and customer views
Shape access around the people using the information and the work each person needs to do.
We first establish where the information lives, how records are identified and updated, and which source is authoritative. A new interface need not discard the existing database.
02 / Existing application
Improve software you already use.
A useful system can still be missing a workflow, a clearer interface, or a connection to another tool. A focused extension may solve the problem while retaining the parts people depend on.
01
Features and workflow extensions
Add the missing step or business rule while retaining the parts people depend on.
02
Clearer interfaces
Help people find information and complete a task with less work around the system.
03
Upgrades and integrations
Review dependencies and connections to see where a focused improvement can support the current operation.
Illustrative improvement: staff can find a record but cannot see its change history. The first improvement could add a view of what changed and when.
03 / Struggling system
Recover or replace a struggling system.
When a system is unreliable or unfinished, the next step is to understand its condition, the data it holds, and the work it must keep supporting. That may lead to fixing a problem, completing a missing feature, or replacing the system a piece at a time.
01
What works
Identify the useful behaviour and information the business still relies on.
02
What fails or remains incomplete
Separate a specific fault from missing functionality or a broader limit in the current system.
03
Available code and data access
Understand what can be inspected and changed before choosing a route forward.
04
What must keep operating
Identify the records, people, and workflows that need a planned transition.
Choose the smallest change that addresses the problem.
The age of a system does not decide its future. The decision depends on how it works and what the business needs next.
Illustrative example
Existing records + current workflow
Useful information; access missing
Add an interface
Keep the useful records and give people a practical view.
Core works; capability missing
Extend the application
Build the missing feature around the existing operation.
Current system cannot support the work
Replace in stages
Check transferred records before switching the workflow.
- Check transferred records
- Switch the workflow
How projects start
Understand the system, then choose the first improvement.
Start with a free fit review. If the requirements are clear enough, I provide a fixed quote directly. If important questions need investigation first, I’ll propose a small planning phase with an agreed scope and price of no more than $500 USD.
Understand what exists
Review the current system, available access, and the workflows and information people depend on.
Choose a useful improvement
If the right change is unclear, we can first agree on an investigation to help decide.
Build and check it
Check the agreed change against representative records, workflows, and operating needs.
Decide what comes next
Introduce the improvement, learn from its use, and decide whether another change would help.
You keep the documented requirements, findings, recommended approach, scope boundaries, and acceptance criteria. When the build is viable and sufficiently defined, the handoff includes a fixed proposal for the first implementation, with timing and operating responsibilities. If the right answer is not to proceed, you receive the reasons and alternatives instead. You can use the handoff with Featherply, another developer, or nobody.
Plan the change around the people who rely on it.
We plan how the change will be introduced, check the records and workflows people rely on, and agree on what to do if a release needs to be rolled back.
Start a conversation
What exists today, and what needs to work better?
I’ll review your message and reply within two business days with any initial questions and a suggested next step. This initial fit review is free.
No paid work starts until its scope and price are agreed and you explicitly approve it.
Privacy and your enquiry
I treat what you share as private and use it only to review your enquiry unless we agree to use it for a project. Share only what you are comfortable sending; a short description or anonymized example is enough to start.
This page may use MaxMind to estimate your country or province from your IP address and adjust its wording. We don’t request precise device location or attach the inferred location to your enquiry. Campaign links can select regional wording independently of your location.