Jadon Jackson / builder

Plant City, Florida · security engineer who builds

Most small businesses don't need a website. They need the thing behind it.

I'm Jadon. I build the working parts: the inquiry that actually reaches somebody's phone, the dashboard a studio owner opens with her coffee, the text that goes out while the customer still loves how the driveway looks. Real software, running in production, for businesses down the road from me.

01

Selected work

ordered by build date
01

Little Hire

Live · app.littlehire.app

Preschools hire constantly and hate every part of it. They post on Indeed, the bill climbs with every sponsored click, and the applicants who show up don't know what a CDA is or why ratios matter. Directors are running a classroom and a hiring pipeline at the same time, usually from a laptop in the office at 6pm.

So I built a hiring platform that only does preschools. A center signs up, posts a role with the things that actually matter (credentials, pay range, hours) and it goes live on a job board built for early-childhood work. Applications come back scored and ranked, résumés parsed on upload. Flat monthly price, three tiers, no per-applicant surprise.

It's a real multi-tenant SaaS: Stripe subscriptions wired through a signature-verified webhook, plan limits enforced by a database trigger rather than a hopeful if statement, and row-level security isolating every center's data from every other center's. An external security probe came back clean: auth gates held, and anonymous reads of the candidate and application tables returned zero rows. That last part is the one that matters, because it's somebody's staff records.

Push to master and it deploys itself. Getting that pipeline honest took finding out it had been quietly failing the whole time while I hand-deployed over the top of it.

  • Next.js 15
  • TypeScript
  • Supabase
  • Postgres RLS
  • Stripe
  • Resend
  • pdf-parse
  • Cloudflare Tunnel
  • systemd
02

Studio OS for Cute Company Photography

Live · in production

A photography studio was running its whole business out of an inbox. Inquiries came in as email, got answered late or not at all, and nobody could say how many turned into booked sessions.

I built both halves. The marketing site at cutecompanyphotography.com is original to the studio, with its own layout, palette and type, not a theme with the logo swapped. Its contact form writes straight into a Supabase-backed dashboard at studio.cutecompanyphotography.com that the owner opens with her coffee. Inquiries land in a pipeline, galleries route through Pic-Time, past clients get rebooking nudges. Magic-link sign-in, so there's no password to lose.

Row-level security on every table, because a studio's client list is a studio's client list. The public site ships a strict Content-Security-Policy and talks to exactly one origin: the dashboard.

The form on the site and the dashboard she works from are the same system. That's the whole point. A website that doesn't write to anything is a poster.

  • Next.js
  • TypeScript
  • Supabase
  • Postgres RLS
  • Resend
  • Pic-Time
  • Tailwind
  • Netlify
03

Juice Melody

Live · juicemelody.com

A Black-owned mobile cold-pressed juice business in Tampa Bay. Storefront live on Shopify, checkout working end to end, and a brand system built around their real bottles and real logo rather than anything generated.

The part I like best is the ad pipeline. Their ad runs on EV charging-station screens around town, which means it has to be an exact 640×800 file, every time. So the ad is an HTML template rendered through a headless browser at 2× and downscaled, so it gets real typography instead of dragging text boxes around. The QR code is generated with high error correction and then scanned back programmatically to prove it works before anything ships.

The ad carries its own discount code, prefixed with the charging-station company's initials, so both businesses can see exactly which redemptions came from those screens. Small thing. It's the difference between a cross-promo and a guess.

Anyone can make an ad. Making one that renders at the exact pixel spec, with a QR you've verified actually scans, is what keeps a client from finding out the hard way.

  • Shopify
  • Admin GraphQL
  • Playwright
  • Python · PIL
  • QR verification
  • Brand system
04

Review Engine

Built · pre-sell

Pressure washers and lawn crews around here rank below competitors who don't do better work. They just have more Google reviews. The bottleneck was never the software, it was the asking reliably happening at the one moment the customer is happiest.

The tool does one thing. Owner finishes a job, opens it on his phone in the driveway, types a name and a mobile number, taps once. The customer gets a text while the concrete still looks incredible.

I wrote the design brief around a 45-year-old standing in direct Florida sun who is tired of being sold to by marketing guys. High contrast, big tap targets, plain words. It should feel like a clipboard, not a startup.

Then the research said the app wasn't the product. The follow-through was. So I froze the build and sold it as a service instead. Knowing when to stop building is part of the job.

  • Node
  • Twilio
  • Mobile-first UI
  • Google Business Profile
05

Proposal Dashboard

Shipped

An interactive client proposal that lives in one HTML file. No server, no build step, works on a plane. Send it as a link or attach it to an email.

The client picks a package, toggles add-ons and watches the total update, types their name to sign, and accepts. That acceptance either opens a pre-filled email back to you or POSTs as JSON to a webhook. Nothing to set up, or fully wired into a workflow, depending on what you need. The structure follows what PandaDoc, Proposify and Qwilr have already proven converts, rather than my opinion about it.

  • Vanilla JS
  • Single file
  • Zero dependencies
  • Webhook-optional
06

Catering Engine

Validating

A food truck makes more on one catering event than on a whole day of service. Most never turn up in catering searches, because their Google profile says Food Truck where it needs to say Caterer. One field, and it decides who gets found.

Before writing any code I pulled the state licensing database (365 active trucks across the corridor), read 840 owner posts, and looked at what the businesses actually winning the map pack are running. The current number one uses a free Google Site with a PDF menu. Their moat is reviews, not web design.

So the spec exists and nothing is built. It ships after two owners have put down a deposit, and not before.

The honest finding was that the demand traced back to one loud post rather than a market. Worth more than a demo would have been.

  • Market research
  • State licensing data
  • SERP analysis
  • Local SEO
07

Content Pipeline

Shipped

A Python toolchain that builds short-form video start to finish: script, voice, captions, music bed, stitched render, plus carousels. It's driven over a Telegram bot, so I can kick off a render and pick it up from my phone.

I built it because making content by hand was the thing quietly stopping every other project from getting marketed.

  • Python
  • FFmpeg
  • TTS
  • Telegram Bot API
  • Auto-captioning
02

How I work

I look before I build

I go find out what the businesses already winning are actually running. Twice now that's told me to build less than I planned, and both times it was right. You're paying me to be correct, not busy.

The site isn't the product

What matters is the inquiry that arrives, the record that sticks around, the message that sends. I build the whole path, not the part you look at.

I think about who's holding the phone

A tool used in a driveway in direct sun follows different rules than one used at a desk. Big targets, high contrast, no jargon. I figure out who's actually using it before I open an editor.

Security isn't something I bolt on after

I work in cybersecurity during the day and hold a Security+. Row-level isolation, scoped keys, least privilege: those go in when the schema does. Retrofitting them onto live customer data is how small businesses end up in a bad week.

I'll tell you when it's not worth it

Sometimes the answer is a $0 Google Business Profile fix and not a project. I'd rather say that and keep your trust than sell you something you didn't need.

You own everything

Your domain, your database, your Stripe account, your customer list. If you and I stop working together, nothing of yours is stuck behind me.

What I build with
LayerToolsUsed in
FrontendNext.js, React, TypeScript, Tailwind, Framer MotionLittle Hire, Studio OS
Backend & dataSupabase, Postgres, row-level security, API route handlersLittle Hire, Studio OS
PaymentsStripe subscriptions, signed webhooks, plan gating in the databaseLittle Hire
MessagingTwilio SMS, Resend email with SPF/DKIM, magic-link authReview Engine, Little Hire
CommerceShopify, Admin GraphQL, discount attributionJuice Melody
AutomationPython, FFmpeg, Playwright, Telegram Bot APIContent Pipeline, Juice Melody
SearchGoogle Business Profile, local SEO, schema markup, SERP auditsCatering Engine, Studio OS
InfrastructureCloudflare Tunnel, systemd, push-to-deploy, NetlifyAll of it

Tell me what's breaking, and I'll tell you straight if I can fix it.

I take on a few projects at a time, around a full-time security job, which means I'm honest about timelines and I don't disappear. If inquiries are getting lost, customers aren't leaving reviews, or your site just sits there when somebody fills out the form, that's the work I do. And if you don't need me, I'll say so.

Start a project
  • Emailaisidehustle23@gmail.com
  • BasedPlant City, Florida
  • ServingTampa · Lakeland · Brandon · remote
  • CredentialCompTIA Security+
  • AvailabilityEvenings & weekends