Skip to the work
ACP Designs StudioCarson Palmer

Tuscaloosa, AL
Property systems studio

ACP Designs Studio

Real work.
Better systems.

I go into the messy parts of property operations and come back with calm, useful systems—built for people, not dashboards.

See the work

Proof, not promises.108 rental units · 4 properties · human approval built in

Editorial field diagram connecting a phone call, work order, checklist, property, and operator
Approved
by human

What the work
supports.

Real properties, real calls, and useful side projects.

108
Rental units

Across four properties where these systems do real work.

24/7
Service

Leasing and maintenance calls across four properties.

03
Side projects

Transfer Portal, HabitForge, and TodoToNotes.

Build trail

1,833
Commits
≈564
Logged build hours

Build snapshot: January 1–July 17, 2026. Commits cover 16 active repositories. Hours use unique 15-minute windows from human-directed AI sessions and Git history.

  1. 01ProjectsLive work, real impact.
  2. 02SystemsEight specialists, one private system.
  3. 03How I workOperations become systems.
  4. 04What I've learnedPatterns worth keeping.

System map · Hermes

Eight specialists.
One operating center.

A self-hosted AI team running on one Mac: property operations, leasing, collections, research, system health, and memory—coordinated through chat and stopped by a human gate before anything leaves the system.

08
Specialized agents
20
Scheduled routines
18
Local background jobs
01
Private chat workspace
One private Telegram groupAsk once. Route to the right lane.

The names are nicknames. Eight lanes in one chat window are easier to run when each one answers to something you can say out loud.

Before I wake

Property data syncs. The morning digest waits.

Through the day

New work becomes a draft, alert, or routed specialist task.

My part

Read the signal. Type APPROVE when the work is right.

Public map. Private IDs, paths, and topic numbers omitted.

One day,
on the clock.

The same day, every day. The systems run the routine so a person only handles the judgment calls.

  1. Property data syncs

    AppFolio numbers land on the Mac before the workday starts.

  2. The digest waits

    One chat message: occupancy, work orders, money, anything overdue.

  3. Email triage

    Gmail is sorted; leasing inquiries get a drafted reply for approval.

  4. Sarah answers the phone

    Leasing and maintenance calls become organized requests, day or night.

  5. Approvals, not busywork

    Drafts and work orders queue up. I read the signal, then type APPROVE.

  6. Follow-up sweep

    Vendors get chased, voice calls get quality-checked, stuck work gets flagged.

  7. The system tends itself

    Backups run, memory logs write, the shared wiki is verified.

  8. The ledger lands

    Late rent, renewals, occupancy, and P&L reports arrive in chat.

Pulled from the live schedule above, rounded to the rhythm of the day. A person owns every outbound decision.

Pinnacle Park
at Northriver

Tuscaloosa, AL · 50 Palmer-managed units · Student living

At Pinnacle Park, calls are answered around the clock, maintenance requests become organized work orders, and every resident-facing message waits for a person’s approval.

The systems on this job

Sarah
Answers leasing and maintenance calls, day or night.
AppFolio Workflow
Turns each call into a work order ready to approve.
Kae
Runs student turnover and move-in checks.
Visit Pinnacle Park
Entrance to Pinnacle Park at Northriver
03

Field-tested.
Iterate. Ship.
Repeat.

  1. 01Observe

    Start in the real workflow.

  2. 02Clarify

    Find the friction and the handoff.

  3. 03Build

    Ship the smallest useful system.

  4. 04Prove

    Test it where the work happens.

  5. 05Improve

    Document, automate, and refine.

04

I build systems that respect people and reality.

Real property is people work. Technology should make it lighter, clearer, and more accountable—not hide it behind another screen.

  • Human approval is the foundation.
  • Useful beats clever.
  • Document the process, then improve it.
  • Measure what matters, then do better.
Blueprint-style illustration of a classic Tuscaloosa water tower

Three signals I keep in every build.

Signal 01

Meet people where they already are.

Phone, email, text, forms, and handwritten notes can all be good inputs.

Signal 02

Make the handoff visible.

A system earns trust when everyone can see what happens next.

Signal 03

Keep judgment in the loop.

Automation prepares the work. A person owns the decision.