Local roots
Computer Engineering studies at UTPA and a Master’s in Information Science from UTRGV.
McAllen · Harlingen · RGV · Remote
Your creator business has a tech department now.
Websites, integrations, software problems, and repetitive work—explained clearly and solved by a local engineer who understands the business behind the technology.
- UTPA
- Computer Engineering studies
- UTRGV
- Master’s in Information Science
- 16+
- years inside a real commerce platform
Local and accountable
START HEREYou explain the problem.Jay figures out the technical part.
What can I bring Jay?
The problems nobody seems to own.
You do not need to know the technical name. Pick the sentence that sounds most like your situation.
01
Something is broken
Website, checkout, login, email, account, app, domain, or connection between tools.
Get help → 02I’m doing too much by hand
Following up, copying information, onboarding clients, making reports, or tracking work.
Make it easier → 03I need a website or tool
A better website, customer portal, internal tool, workflow, calculator, or original idea.
Plan it with Jay → 04I need ongoing tech help
A dependable technical person to call without hiring a full-time employee.
See if it fits →Flagship proof
Not a demo project.
A 16-year operating system.
Jay has spent more than sixteen years working across the public website and back-office systems of a McAllen-based manufacturer—supporting education, e-commerce, customer accounts, and different partner roles as the business evolved.
View the private, non-indexed case study →Public experienceEducation · SEO · products
CommercePayments · orders · fulfillment
Partner journeysPractitioners · resellers · distributors
Business rulesRoles · pricing · workflows · data
Julio “Jay” Johnson
Freelance Tech Partner & Systems Engineer
Friends and clients call me Jay. I’m based in McAllen and Harlingen, and I help creators and owner-led businesses solve the technology problems that sit between websites, IT, operations, and software.
Business memory
Sixteen years maintaining and improving a platform that had to keep working while the company changed.
Plain language
No need to arrive with a technical specification. Start with what is happening and what you wish happened instead.
Bring me the messy version