JPR Code
Big software. One engineer.
I'm a senior software engineer who builds real websites, apps, first versions of new products, and automation for small and mid-size businesses, the kind of software usually reserved for companies with whole teams.
Who I work with
Small and mid-size businesses come to me with something they need built, or an old system that's starting to creak. I build the software that fixes it, built to last, not just to launch.
Services
- Websites & apps
Get software your business can actually run on.
A real website or app that holds up once real people are using it. I handle the whole thing, from what your customers see down to the parts running quietly behind it. And I build it to be easy to change later, because your business will.
- First versions of new products
Go from idea to something real customers can use.
We find the smallest version of your idea worth building, build it well, and get it in front of real customers. You learn whether it works before you've spent a year and a fortune finding out.
- AI & automation
Hand the repetitive work to software.
If your team burns hours moving data between systems by hand or answering the same question over and over, a lot of that can run itself. I add AI where it genuinely saves time or money, and I'll tell you where it won't.
- A senior engineer for your team
Serious engineering help, without a full-time hire.
When your team is stretched thin or a project needs an experienced hand, I join in, get up to speed fast, and build alongside your people for as long as you need me.
Selected work
A few problems I've solved for the businesses I work with, plus the open-source software I help maintain in my own time.
-
A fragile spreadsheet, replaced
One bad entry in a shared spreadsheet could break the whole process. I replaced it with a simple app that does the job in a few clicks and doesn't let a typo take it down.
-
The end of double entry
A team typed every number twice, once on paper, once into their database. I connected the two, so it is entered once and lands straight in the system they already use.
-
An aging system, made reliable
I took a large, dated system, rebuilt it on a modern web platform, and added automated checks that catch problems before a user ever sees them. It's reliable now, and there's room to keep building on it.
-
Idea to a working v1, fast
I built a high-priority product with a team and got a working first version in front of real people fast, instead of chasing perfect for months.
Open source
The Community Platform
Maintainer
When I'm not building for clients, I help maintain the open-source platform behind Precious Plastic and the wider One Army movement: a live product a global community depends on every day.
How it works
-
We talk
It starts with a free 30-minute call. You tell me what's going on, I ask a lot of questions, and we figure out together whether there's a project worth doing here.
-
You get a plan
I put together a plain-language plan: what we'll build, what it costs, and what you'll see along the way. You'll understand every line of it before any work starts.
-
You watch it take shape
I build in short stretches and show you real, working progress as it happens. You won't wait for a big reveal at the end. If something's off, we catch it early, while it's still cheap to fix.
-
We launch, and I stay
Your software goes live and I don't disappear. I'm here to keep it running and make it better for as long as you want me, and if you'd rather take it from here, that's completely fine.
About
Jacob Roberson
Founder & principal engineer, JPR Code
The engineer you talk to is the engineer who builds it.
JPR Code is me, Jacob Roberson. I'm a senior software engineer, and I've built software at just about every scale: in-house at established companies, on contract for Fortune 500 corporations and larger private companies, and side by side with small businesses.
That range taught me what actually holds up once real people depend on it, and how to build it so it keeps holding up.
I keep my client list short on purpose, so your project gets real attention from the person actually building it, start to finish.
FAQ
What if I'm not technical?
Most of my clients aren't, and that's fine. Part of my job is translating. I explain what I'm building and why in plain English, and no question is too basic to ask. You won't need to learn any jargon to work with me.
How much does it cost?
Every project gets scoped and priced on its own, because a small automation and a full product cost very different things. We talk through it on the intro call, so you know where you stand before you commit to anything.
How do we communicate during a project?
Directly, with me. There's no account manager relaying messages and nothing gets lost in a handoff. When you have a question, you ask the person actually writing the code, and you get a straight answer.
What happens after launch?
I stick around. Software needs care after it goes live: small fixes, updates, new ideas as you go. We'll shape what that looks like for your situation.
Do you work with existing systems or an existing team?
Yes, often. Some clients need something brand new. Plenty need help with software they already have, or a senior engineer working alongside their own team. I'm comfortable stepping into work that's already underway.
Tell me what you're trying to build.
The first step is a free 30-minute call. We talk through your situation and I tell you, straight, whether I'm the right person for it. It's just a conversation, and you're under no obligation to hire me.