About Me
I scope the work, build it, and hand it over in your name.
I am Trenton Taylor, a software engineer. I build software to order, repair conversion tracking that reports the wrong numbers, and run outbound email for companies anywhere.
How It Usually Goes
Work like this usually goes to a team you never meet.
An agency sells you the work, and the people who scoped it hand it to whoever is free. The person answering your email in month three has never opened the code.
The other option is a contractor who takes the job, finishes it, and leaves you with something nobody can pick up: no repository you own, no account in your name, no written record of what was done.
I take the first call, do the work, and answer your messages while it runs. Everything is handed over in your name with a written account of what was done, so you are not tied to me to keep using it.
Trenton Taylor
Owner
I was a district manager. We needed software, so I built it. I left that job to do this full time. I now build software to order, repair conversion tracking, and run outbound email for companies that need one of the three.
The Numbers
Anywhere
Every part of this happens over calls, screen shares, and email, so where your company sits makes no difference to the work or the price. Nothing needs to be signed in person.
How I Work
What you get
on every job.
Three things that hold whichever service you buy, and whatever the work costs.
You own what gets built
The repository, the domains, and the accounts are registered in your name. Another engineer can pick the work up after me without asking me for anything.
Your messages land on my phone
No account manager sits between you and the work. You send a message, it lands on my phone, and the answer usually comes back inside the hour.
A price and a date before anything starts
Both come back in writing after the first call, and neither moves once you have agreed to them unless you ask for something that was not in the scope.
Process
Four steps from
first message to handover.
This is the whole of it, start to finish. There is no onboarding sequence behind it.
You get in touch
Tell me what the work is and what it has to do when it is done. A few sentences is plenty. There is no thirty-field intake form.
You
Send me a message
Me
Reply usually within the hour
We go through it
A call, then a read of how the job runs now. I ask what I need to scope it, and say so if the work is not worth doing.
You
Walk me through the job
Me
Ask what I need to price it
You get a price and a date
What gets built, how long it takes, what it costs, and what is not included. In writing, before anything is charged.
You
Read it and say yes or no
Me
Send the scope, the price, and the date
I do the work and hand it over
You see where it stands as it goes rather than in a status email. At the end everything is in your name, with a written account of what was done. Outbound is the one that keeps running; the other two end when they are done.
You
Review as it goes
Me
Build, test, and hand over
Get in Touch
Tell me about the work.
A few sentences on what you need and what it has to do when it is done. You usually get a reply within the hour: a straight answer on whether it is a fit, then a scope and a price.