Skip to main content

Disabled Army veteran · Independently operated

Hillsboro, Oregon

Keep the signal.
Build what matters.

I’m Junior Fortunato, a disabled U.S. Army veteran. I kept satellite links running; now I design websites for local businesses and build software that holds up.

U.S. Army veteran2014–2018
The U.S. Army Senior Space Badge: a pair of swept silver wings flanking two gridded globes, a delta point up between them, two elliptical orbits crossing behind, and a single star above for the senior grade.
Junior Fortunato · FounderSenior Wideband Controller
The 1st Space Brigade shoulder sleeve insignia: a shield bearing an eagle with spread wings over a gridded demi-globe, crossed orbital paths and a downward arrowhead, with a star above.1st Space Brigade

Satellite communications then. Business systems now.

Chart: the local sky over Hillsboro, with the site’s own satellite mark above the horizon line, in view, and a ground station uplinked to it — the maintenance page draws the same sheet with the mark below the line.

I work inside a company that can’t afford downtime. So I learned to build things that don’t break — and to explain them to people who don’t code. That’s the whole job, really.

What I can help with

Selected work

The work comes first.

A business that runs on it. An experiment that tests it. A site you can try yourself.

02Python · C# · Go · TypeScript

One product, built four times.

The same access-control console, on purpose, in four languages — identical screens, the same security model underneath, bar one permission key I left mismatched rather than edit a repository to flatter the result.

03You’re using it

This site is the product.

Read project stories and engineering notes, then try the AI console demo with sample data in your browser. No account needed.

A few numbers, with their context.

40%Less time on paperwork.My informed estimate
What this includesI replaced a paper-and-spreadsheet process at a healthcare company with software I built. That is the drop in administrative processing time.
235People using my software every working day.
What this includesRoughly 235 of them: 150 caregivers, 45 office staff, 20 nurses, and smaller teams besides, plus external staff on top. The 500 clients whose records it holds don’t sign in, so they are not counted here.
4Languages, one product.
What this includesI built the same access-control tool four separate times — Python, C#, Go and TypeScript — to see what the language really changes.
7Platforms designed, built and kept running.
What this includesNot prototypes, not tutorials — two are publicly live right now and you’re on one of them; the rest are private or internal. Named on the work page: Pelican, Kingfisher, Sharpbill, Goldfinch, Merlin, this platform, and Usage IQ.
Where the figures come from

Every number here is something I built or something I was in the room for. The 40% is my own estimate rather than a stopwatch study — I worked inside that company before the software and after it, and that is the size of the change. I would rather tell you where a figure came from than round one up, and where I have no number I left the sentence out. It is the one I’d most like to be asked about.

Two ways to start

What does your business need?

A better first impression, a better way to get the work done, or both. We’ll work out the right starting point together.

And someone to see it through.

From understanding the job to supporting the people doing it.

Learn your business first.

I watch how the work gets done, find the repeated steps, and work out what is worth changing.

Build it.

Websites and business software, from the screens your team uses to the database behind them.

Train your people.

Plain-language documentation and hands-on training with the people who will use the software.

Keep it running.

Hosting, backups, upgrades, and someone who knows the system when something needs attention.

Prove it.

Records of what happened and who did it, collected while the work happens.

One person. Personally responsible.

A veteran behind the work.

Junior Fortunato with dark curly hair and a beard, wearing a charcoal shirt in a warmly lit workspace.
Junior Fortunato / Founder

Army communications. Business owner. Working IT director.

I run technology and compliance for a healthcare organization. Northwest Fortune Solutions brings that same hands-on work to businesses that need more than a vendor—and don’t need a whole department.

About Junior Fortunato
From Army communications to running business systems

I was a Senior Wideband Controller in the U.S. Army from 2014 to 2018 — the person who keeps the satellite and radio links up. Drone operations, ships, submarines. I qualified across six critical positions and became my unit’s youngest senior controller.

What I took from it wasn’t discipline in the poster sense. It was this: when the link goes down, nobody wants your explanation. They want it back. And then they want to know why, in writing, so it doesn’t happen twice.

Since 2022 I’ve directed technology and compliance for a healthcare organization — the team, the budget, the vendors, the audits, and the software. And I still write the code. Northwest Fortune Solutions is that same work, done for people who need it and can’t hire a whole department.

How I test the work, including my own mistakes

How I check the work

The mistakes belong
in the write-up, too.

One is a bug I shipped and published. One is a warning I built to make my own demo look worse.

01

I found a privacy bug in my own code, and then I published it.

I point my own AI tooling at my finished work and tell it to break in, and every finding it raises goes to a second one told to refute it. A location feature failed that pass: it was showing people’s exact position to more roles than it should have. Fixed the same day, with a test that fails if anyone ever undoes the fix.

The finding, in full

02

My AI demo tells on itself.

If no real AI service answers, the demo says so on screen, in the moment — not a footnote. A demo that quietly fakes a result is worse than no demo at all.

Try it and watch it admit it

If you write software for a living

The engineering notes.

There’s a lot of mechanism behind this site, and none of it is on the front page. That was on purpose: it was crowding out what a hiring manager actually needs.

None of it got deleted. It’s one click away, in more detail than is strictly reasonable.

  • How signing in is kept separate from being allowed.
  • Why the live connection and the ordinary screens had to be taught the same rule the hard way.
  • What actually differed across four rebuilds of the same product.
  • And the findings from the audit I ran on myself that survived a skeptic.

Explore the decisions behind the build.

Let’s talk about the work

Let’s get to
the useful part.

Show me the spreadsheet you keep rebuilding, the website you’ve outgrown, or the process that takes too many steps. We can start there.

I answer my own email, usually the same day.

What we’ll cover in 30 minutes
The work
What you do today, and where it gets difficult.
The fit
Whether a website, custom software, or a smaller fix makes sense.
The next step
What I’d need to understand before putting a proposal together.

30 minutes, directly with me.

Looking for my résumé? Request my résumé by email

The résumé is not posted as a public download. This link opens an email so you can request a copy. Project write-ups and engineering notes are available to browse here without an account.