How we work - Know what is happening at every step
A clear scope, working software early, and a short update every week keep the project understandable. You know what is finished, what is next, and when I need a decision from you.
Understand
First, I learn how the work moves through your business. Who does what? Which systems are involved? Where does the team lose time, re-enter information, or work around a tool that no longer fits?
Then I map the workflow we're fixing and write a plain-English scope. It covers what I will build, what can wait, what it costs, and how long it should take. I use fixed scopes and fixed prices wherever the work is predictable enough.
You will also get a build-or-buy recommendation. If a $40-a-month product handles the job well, I will point you to it before you spend real money on custom software.
Included in this phase
- Free initial consultation
- Workflow mapping
- Build-vs-buy recommendation
- Written scope and fixed quote
Build
I work in short cycles and put something visible in front of you early. Within the first couple of weeks, you should be looking at real screens and testing the important parts of the workflow.
Each week, you get a short update covering what is finished, what is next, and any decision I need from you. When you have a question, you ask the person writing the code.
Small adjustments are part of the work. If a request changes the size of the project, I put the cost and schedule impact in writing before I build it. You decide whether it belongs in this release or a later one.
Deliver & support
We plan launch around your business calendar and test with your real data and team before anything goes live. I handle the switchover and stay close during the first days of normal use.
You get everything: the code, the accounts, the credentials, and documentation written for whoever comes after me. If you ever want another developer to take over, they'll have what they need.
After launch, choose the level of support your business needs. I can provide ongoing maintenance and changes, or you can get in touch when a specific need comes up.
Included in this phase
- Testing with real data. Software gets tested against your actual workflows and edge cases before launch, with your team involved. That catches surprises while they are still easy to fix.
- Full ownership. Code, accounts, credentials, and documentation are yours from day one. You could leave at any point and take all of it with you.
- Support that fits. A monthly support arrangement if you want a standing safety net, or hourly help when you need it. Retainers are optional.
Principles - The rules the work follows
These are the standards I hold the work to, and you should hold me to them too.
- Documented scope. Estimates include the parts I know and the parts that still need investigation. I explain the uncertainty before it affects your budget or schedule.
- Boring technology. I choose mature, widely used tools with a good chance of being supported for years. New technology needs a business reason to earn its place in the project.
- Small releases. You see useful pieces of the system as they are completed. Feedback arrives while changing direction is still inexpensive.
- Plain English. Technical choices come with a practical explanation of the cost, risk, maintenance, and effect on the people using the system.
- Your ownership. The code, data, accounts, and documentation belong to you. I set projects up so you can access and transfer each part without depending on Pineflux.
- Maintainable first. Clear structure, readable code, and current documentation reduce the time it takes to fix or extend the software later.
What is slowing your business down?
Send me a few details about the problem, the tools involved, and what a good result would change. I'll reply within one business day with a useful next step.
Based in
- Seattle, WA
Working remotely with clients
across the US