About the builder

Hi, I’m Aedyn. I build practical software for real businesses.

I’m a developer with Georgia roots, a mathematics student at the University of Michigan, and the person you work with from the first conversation through the final build.

I like the part of software that starts before the code: learning how someone actually works, finding the friction, and turning it into something simpler. That is why I started CapSys.

Tell me what you need See the Southside project

Portrait of Aedyn Smalley — Aedyn SmalleyGeorgia roots

Where I’m coming from

Curious about systems, serious about the useful details.

My background is rooted in Georgia, and I have always gravitated toward figuring out how things fit together. Mathematics gives me one way to do that; software gives me another, more immediate one.

My hands-on background spans web development, Linux, cloud environments, automation, Python, and Bash. I enjoy moving between the visible part a customer uses and the systems behind it that keep everything running.

CapSys is a one-person studio, and I’m early in my career. I don’t dress either fact up. You talk directly with me, I stay close to the details, and the scope stays grounded in what your business actually needs.

Education & toolkit

Learning formally. Building constantly.

The classroom sharpens how I reason. Building sharpens how I communicate, make tradeoffs, and finish something another person can depend on.

Now

University of Michigan

B.S. in Mathematics · Expected May 2029

2025

Foundry Academy

3.75 GPA

Web applications
Linux systems
Cloud deployment
Automation
Python
Bash

A project that made it real

Southside Safe Lock & Door

For Southside, a commercial locksmith, I built a cross-platform operations app around the work the team was already doing: tracking inventory, recording time against jobs, and giving an administrator a clear history of what changed.

The system brings stock counts and profit-margin details, a job-linked time clock, and an admin view for shifts and inventory activity into one focused workflow.

That project is the clearest example of what I want CapSys to do: take a specific, everyday workflow and turn it into software that feels natural to use.

View the project screenshots

How I approach the work

Small-studio attention, without the theater.

Understand the work first

The useful question is not “what feature can I add?” It’s “what is slowing this business down?” I start there.

Keep the scope honest

Not every business needs a giant system. I would rather build the smaller thing that solves the real problem well.

Make it understandable

Good software should feel clear to the people using it. I explain tradeoffs plainly and avoid complexity that does not earn its place.

Let’s make something useful

Have a process that wastes time, or a site that no longer fits?

Tell me what is getting in the way. I’ll answer directly, keep the scope practical, and help you figure out the right next step.

Start a conversation