01
Product features
New customer workflows, operator tools, account functionality, and substantial additions to an existing product.
Senior-level contract software engineering · Edmonton + remote
Senior-level engineering for the product work you need to ship.
I build substantial product capabilities across frontend, backend, databases, integrations, payments, and operations.
Founder and product engineer behind Full Stack Storage.
Best suited to SaaS teams and established businesses with an important cross-stack capability to ship, but no need for another full-time engineer.
What I can own
One important piece of software, taken from problem to production.
I take on substantial, clearly defined product work that can cross frontend, backend, data, integrations, and operations. You get one engineer responsible for understanding the requirement, building it, integrating it, verifying it, and getting it ready to ship.
Typical work I take on
02
Payments and billing
Subscriptions, invoicing, refunds, webhooks, reconciliation, collections, and other workflows where money and state have to stay correct.
03
Integrations and internal tools
API integrations, dashboards, approval flows, reporting, and software that replaces fragmented manual processes.
04
SaaS architecture and foundations
Multi-tenancy, authorization, data isolation, background jobs, migrations, and structural work needed as a product grows.
I can also diagnose, continue, or complete substantial work in an existing codebase when the necessary access and context are available.
Engineering proof · Flagship system
Full Stack Storage
Controlled launch hardening
I am the founder and product engineer behind Full Stack Storage, a multi-tenant operating and commerce platform for independent self-storage businesses.
Business status
Currently in controlled launch hardening. Presented here as engineering proof, not as a customer-traction claim.
Engineering scope
01
Go application services, scheduled work, and durable background processing
02
Multi-tenant PostgreSQL architecture, Row-Level Security, authentication, and authorization
03
Next.js and React interfaces for operators, customers, and tenants
04
Payments, billing, reconciliation, and refunds, with tenant payment flows designed to preserve SAQ A eligibility through processor-hosted payment elements and iframes that keep raw card data out of both Full Stack Storage and tenant websites and servers
Core stack
Go
Next.js
PostgreSQL
TypeScript
Linux
Infrastructure
Vultr
System shape
01Operator / Customer / TenantProduct interfaces
→
02Application APIsServices and workflows
→
03PostgreSQLData and tenant boundaries
→
04Connected systemsPayments · Email · Signing · Storage · Background work
Commercial and engineering history
Additional engineering proof
Some earlier systems were built for private businesses, so I describe their engineering scope without publishing client code, data, or proprietary screenshots.
Repeat paid client engagement
Private logistics operations platform
4 paid sprints approximately 600 hours
September 2023 onward
- Problem
- An existing logistics database needed to become a usable, multi-user system for tracking shipping-container activity.
- Engineering responsibility
- Built and extended the Django application across four paid development sprints, including restricted access for outside businesses and tenants.
- Technical challenges
- Two-factor authentication, role-based permissions, protected view-as-user support tooling, normal access controls, and comprehensive audit trails.
- Result
- A multi-user operational application that brought the existing database online for internal staff, outside businesses, and tenants.
Stack
Python
Django
JavaScript
DevExtreme- Linux
Infrastructure
Azure
Reusable website integration system Multi-deployment Lit, TypeScript, and PHP integration architecture.
- Problem
- Independently hosted websites, including WordPress and Squarespace sites, needed a repeatable way to connect to a third-party self-storage management API without requiring a platform-specific implementation for each site.
- Engineering responsibility
- Built a reusable integration package spanning frontend components, application state, PHP, and deployment tooling.
- Technical challenges
- Heterogeneous hosting and CMS environments had to share one architecture and receive controlled updates from a shared source using a GitHub token.
- Result
- A drop-and-deploy integration model designed for websites operating in environments I did not fully control.
Stack
- TypeScript
Lit
Vite
Zustand
PHP
The engagement
Start small. Make the work explicit.
Establish fit and context, define the work, then deliver it progressively.
-
01
Fit
Confirm the work, access requirements, schedule, and available capacity align.
-
02
Technical orientation
Use up to three complimentary hours to understand the system, dependencies, constraints, and desired behaviour.
-
03
Define the capability
Set boundaries, acceptance criteria, priorities, and the first delivery target.
-
04
Build and iterate
Implement, integrate, verify, and deliver progressively.
Continue with the next defined piece when it remains valuable, or conclude cleanly.
During paid work, you receive a concise written update covering progress, blockers, important decisions, next work, and hours used.
Technical project orientation establishes context and dependencies. Confidentiality, tooling, and access boundaries are agreed before repository or production access. Orientation does not include implementation or production changes.
Typical engagement
Working with me
CAD$95/ hour
One fractional client slot
Typically 8 to 12 hours per week
- Start with one defined capability
- Up to 3 hours complimentary technical project orientation
- Weekly hour caps available
- No long-term commitment, continue only while useful
- Professional invoices from Featherply Inc. in CAD, with applicable taxes where required
- Standard development tooling included
Brad Conklin
Founder / Product Engineer
Edmonton, Alberta
I spend most of my time building Full Stack Storage through Featherply Inc. and keep one outside client slot for substantial product work. I work from Edmonton with clients remotely.
Bachelor of Science with Specialization in Computing Science University of Alberta
Engineering safeguards
Modern tools. Accountable engineering.
My workflow is AI-augmented. I use modern tools to move through investigation and implementation while remaining responsible for architecture, integration, verification, confidentiality boundaries, and delivery.
How this works in practice Verification, confidentiality, and project safeguards.
Engineering responsibility
I use AI assistance during investigation, implementation, testing, debugging, and documentation. Generated output is not accepted simply because it compiles or looks plausible.
Project data and tooling
Before access begins, we agree on confidentiality, source-code, data-handling, and tooling restrictions. Client-controlled or dedicated tooling can be used where required.
My standard tooling is included in the rate. Projects that prohibit AI-assisted development entirely are generally not a fit.
Start a conversation
What are you trying to ship?
You do not need a finished specification. Tell me what you are building, what the system looks like today, or where the scope is still uncertain. We can determine whether there is a practical first scope and a good fit.
- Architecture review and inherited code can be part of technical orientation when sufficient context is available.
- I normally reply within two business days.
- No paid work begins without an explicit agreement.
Prefer email?