I build the system that runs the work your team repeats every week.

For NYC and NJ property and real-estate teams with work moving by hand between inboxes, spreadsheets, and property software. It runs on a schedule. Anything that touches a tenant or a payment waits for a human to approve it.

JT Somwaru

Who I help

Where the first build usually lands

The first build is usually one workflow that runs every week and depends on one person being available.

Recurring work that runs on one person

One person holds the workflow, and it moves when they get to it. I build the version that runs on a schedule, so it stops waiting on someone to be at their desk.

Status dashboardsInbox routingApproval queues

Construction and real-estate operators

The completion figure people quote in the meeting came from a cell somebody set by hand, and it went stale the moment the detail underneath it changed. I build the dashboard that works it out from the detail instead.

Job dashboardsStreetEasy researchOwner updates

Property and family-office operations

Nothing has complained, so everyone assumes the COI chase is still working. I build the expiration and renewal workflow, and it runs inside your own environment.

COI trackingRent readinessAudit trails

Client work

What was manual, what runs now, and who approves it.

Where a figure is missing it is because it was not measured in a way I can hand you.

Problem

A marketing analytics firm needed two client dashboards, a dashboard onboarding playbook agent, and a QA agent, all inside a fixed four-week scope.

What was built

All four, in scope. The QA agent was validated against a controlled test plan written by the client's technical lead.

Independently re-verified by the client's technical lead on client systems before acceptance. Against his test plan the QA agent identified every seeded defect, plus eleven previously unknown defects in existing production code, all confirmed and fixed.
QA Agent and Client Dashboards
Fixed ScopeQADashboardsPaid client work

Problem

A New York City property management firm needed automation around sensitive back-office work without moving financial or resident records into another SaaS layer.

What was built

Self-hosted automation running inside the client's own environment, starting with insurance expiration tracking and daily exception summaries for review.

Daily production run, with exceptions summarized for review
Local-First Property Operations Automation
Self-hostedAudit TrailProperty OpsActive client work

Problem

A construction firm was assembling progress reports by hand before every stakeholder check-in.

What was built

Construction progress dashboard turning field updates into live status visibility and stakeholder reporting.

Live dashboard for active job-site visibility
Construction Progress Dashboard
DashboardConstruction OpsClient WorkPaid client work

Workflow Audit

Five business days. One named workflow. A clear build decision.

Pick the workflow that costs you the most hours. I spend five days mapping how it actually runs, not how it is supposed to run. At the end I tell you what to build first, or whether to build at all.

5 days

timeline

1

workflow

30 days

credit window

Fixed audit fee

$1,500, paid on signature and credited to the build if signed within 30 days.

Book a 20-minute workflow call

Workflow map

The real path. Which report anyone actually trusts, and where work sits waiting.

Exception inventory

Everything expired, missing, or waiting on an approval, with the reason it stopped and who owns it.

Build-or-do-not verdict

Sometimes the answer is do not build yet. If the inputs are dirty, automation will move the mess faster. I will tell you that instead of selling you a build.

Fixed-price build scope

If it is ready, you get one build at a fixed price, with what counts as done written down before I start.

How I work

The first days go into deciding what to build. That is where these projects usually go wrong.

01

Map the real workflow

I follow the work. Which file, which inbox, who approves it, and what happens when the data is wrong. The documented process and the real one are rarely the same.

02

Rank the bottlenecks

What it costs to run by hand, and how dirty the inputs are. Some of these will not be worth automating and I will say so.

03

Scope the first system

One build, at a fixed price, with what counts as done written down before I start.

04

Build it into production

Dry runs and logs first. Then a human approval step anywhere money or tenants are involved.

About

I spent six years as a Business Systems Analyst at Spectrum Enterprise. The hard part was almost never the software. It was working out who owned what, and which exceptions everyone had agreed to handle by hand.

That is the same job now, with AI in it. The systems I build log what they do and stop for a human where money or tenants are involved. A build I have checked myself is not finished. Somebody else has to be able to check it.

Experience

Independent

AI Implementation Consultant

Sep 2025 – Present

Spectrum Enterprise / Charter Communications

Business Systems Analyst

Jun 2019 – Aug 2025

Northeastern University

Data Analytics Certificate

2019

Ithaca College

BS Sport Management, Minor Legal Studies

2014 – 2018

Client Results

Construction and real-estate client

Built a live AI dashboard for an active construction program, and separately automated a recurring market-research workflow.

Property operations client

Building local-first automation infrastructure for sensitive back-office workflows: dedicated workflow machine, audit trail, human-in-loop controls, and recurring compliance automation.

Tools & Systems

AI & Automation Stack

Salesforce AgentforceAgentScriptn8nClaude APIOpenAI APIHubSpot CRMGoogle Sheets APIOpenClaw

Adjacent Technical Fluency

PythonSQLREST APIsVercel

Start with one workflow.

Tell me the workflow that eats the most hours. I reply within 24 hours with whether it is a fit for an audit and what I would need to map it.

jtsomwaru@gmail.com
Book a workflow call

Response within 24 hours.