Available for new builds · Buffalo, NY

Your team should be growing the business, not keeping a spreadsheet alive.

I take the manual data entry, the daily spreadsheet upkeep, and the processes your team runs by hand, and I build systems and custom dashboards that handle all of it. You get your time back to actually grow.

Book a callWhat is the manual work costing you?
Octavian Ideas/Matthew Ryan · Technical Architect & Automation Engineer
Getting businesses off spreadsheets and manual entryCustom dashboards built around your exact use caseProcess automation and workflow engineeringCRM integration and webhook architectureDatabase design and async event processingOperational analytics and live reportingMulti-tenant SaaS architectureDocuSign and contract automationBackend systems and API design (TypeScript, Node.js)Partner and admin portal developmentMCP servers and custom Claude toolingAI training for non-technical teamsAI-assisted curriculum and lab manual developmentMachine learning and iOS app developmentGetting businesses off spreadsheets and manual entryCustom dashboards built around your exact use caseProcess automation and workflow engineeringCRM integration and webhook architectureDatabase design and async event processingOperational analytics and live reportingMulti-tenant SaaS architectureDocuSign and contract automationBackend systems and API design (TypeScript, Node.js)Partner and admin portal developmentMCP servers and custom Claude toolingAI training for non-technical teamsAI-assisted curriculum and lab manual developmentMachine learning and iOS app development
ICustom dashboards

Get off the spreadsheet. Watch the business in real time.

When the data lives in Excel and the same numbers get re-typed by hand, the team spends its day maintaining instead of scaling. I build custom dashboards designed around your exact use case, so the work that keeps you treading water runs on its own and your time goes back into growing.

No more keying the same numbers into a spreadsheet twice.
The metrics that matter to your business, live, in one place.
Built around how your team actually works, not a template.
operations.dashboard
Live

Tasks automated

0

Hours / week back

0

Manual entry

100%

down from 100

Throughput

+386%

By day

0%

On autopilot

Ops running without manual touch

Invoicing100%
Customer comms96%
Outreach88%
Reporting92%

Activity

  • Invoice generated · Job #4821
  • Realtor sequence triggered
  • Payout calculated · The Lodge
  • Webhook synced · SmartMoving
  • Day-of email queued · 2 moves
IIWhat I do

I find the process living in a spreadsheet or in someone's head, and replace it with something that scales.

01Getting businesses off spreadsheets and manual entry
02Custom dashboards built around your exact use case
03Process automation and workflow engineering
04CRM integration and webhook architecture
05Database design and async event processing
06Operational analytics and live reporting
07Multi-tenant SaaS architecture
08DocuSign and contract automation
09Backend systems and API design (TypeScript, Node.js)
10Partner and admin portal development
11MCP servers and custom Claude tooling
12AI training for non-technical teams
13AI-assisted curriculum and lab manual development
14Machine learning and iOS app development
IIIThe cost of doing it by hand

Put a number on the manual work.

Two inputs, one number. It will not be exact, but it is usually closer than people expect, and it is the number worth comparing a build against.

hrs

Add up everyone who touches it, not just one person.

$

Salary plus taxes, benefits, and overhead. Usually well above the hourly wage.

Annual cost of that process

$23,712

That is what the manual version costs every year before anything goes wrong. It is the number worth holding a build up against.

624 hrs

spent on it per year

$1,976

burned per month

16 weeks

of full-time work

See what it costs to remove

Loaded hourly cost means salary plus taxes, benefits, and overhead. For most office roles it lands well above the hourly wage.

IVSelected work

Systems shipped, from solo founder builds to a publicly traded payments platform.

Each one took a manual, error-prone process off the team and made it run itself. Expand any card for the full build.

Semres logo

Semres

Co-Founder · Current

semres.com

One integration and automation layer that sits between a moving company's CRM and its entire customer lifecycle, so the growth work runs without a dedicated ops hire.

1 layerany moving CRM, one codebase

What was built

  • Built a canonical event model that maps any moving company CRM (currently SmartMoving and Chariot Move) into one unified data structure, so automations are written once and run across any tenant.
  • Automation engine handles customer drip emails, realtor prospecting, referral partner management, and lead prospecting, all triggered by canonical CRM events.
  • Secure multi-tenant architecture with strict data isolation, so no tenant's data is ever visible to another.
  • Cloud infrastructure with async webhook processing, continuous monitoring, automatic retries, and managed backups.
  • Reporting and translation layer gives consolidated, live analytics across the customer, realtor, and lead pipelines.

Impact

Turns automation built for a single client into a repeatable product for the whole moving industry. Companies on the platform stop touching customer communication, realtor outreach, and prospecting by hand.

Multi-tenant SaaSCanonical event modelAsync webhooksTypeScript, Node.js
WNY Moving logo

WNY Moving

CTO · Current

wnymoving.com

Full back-end automation and operations infrastructure for a moving company that was running its books in Excel.

0manual entry, books always live

What was built

  • Replaced all Excel-based bookkeeping with a live back-end portal that auto-syncs from SmartMoving over webhooks and API. The books are always current with zero manual entry.
  • Automated customer communication: contextual, timed emails at every stage of the move (pre-move prep, day-of confirmation, post-move follow-up) with no staff involvement.
  • Built a realtor prospecting engine that pulls new listings from the USA Home Listings API, cross-references existing contacts to avoid duplicate outreach, and sends personalized intro sequences.
  • Realtor lifecycle management: once a realtor responds, they move into a managed pipeline with follow-up sequences and partner onboarding.
  • Outreach emails include custom video messages from ownership, branded and auto-populated with listing data.

Impact

Sales and operations no longer touch outreach, follow-up, or customer communication. The realtor pipeline grows on its own in the background, building referral relationships that compound over time.

SmartMoving CRMWebhook syncRailwayEmail automation
4.0 Storage logo

4.0 Storage

Technical Analyst · Current

fourohstorage.com

Took a student storage business that ran on spreadsheets and rebuilt its operations as a self-running system.

under 1 minto log a job, fully on-site

What was built

  • Replaced manual Excel entry with a custom site. Staff key in a student job on-site in under a minute, the student signs digitally, and the invoice is generated and emailed automatically.
  • Scheduling, invoicing, payment collection, and customer communication all run on their own from job creation forward.
  • Killed the dual-entry problem, where the same data lived in a spreadsheet and had to be re-typed for invoicing and communication.
  • Built to scale with volume. The same workflow handles 10 jobs or 1,000 without adding headcount.

Impact

The business went from manual spreadsheet entry on every student job to a system where staff touch a job once. Everything downstream is automatic, with a clear path to scale next season without hiring for operations.

Digital signingAuto-invoicingJob workflowPayments
Skyway Vending logo

Skyway Vending

Founder · Current

braceyskyway.com/vending

Founded and operate a nightlife vending company across Buffalo and Hamburg, and built the entire operations platform from scratch.

2 citiesBuffalo and Hamburg, one system

What was built

  • Built a custom admin dashboard for internal operations: real-time inventory, run-rate analysis by SKU, location performance, automated reorder triggers, and financial reporting.
  • Built a partner portal for bar owners: a clean login showing raw revenue, payout based on the revenue-share rate set at onboarding, and location-level performance.
  • Revenue-share logic is fully automated. Once the rate is set, every payout is calculated and surfaced with no manual work.
  • End-to-end visibility from machine inventory to partner payout in a single system.

Impact

Every payout is calculated automatically, and ownership sees the whole operation, from inventory to partner cut, on one dashboard.

Admin dashboardPartner portalInventory analyticsAutomated payouts
Nuvei logo

Nuvei

Technical Architect · NASDAQ: NVEI

Embedded inside a publicly traded payments platform processing billions in volume, going team to team to map and automate manual operational processes.

months to 3 daysCRE onboarding cycle

What was built

  • Rotated through UI/UX, engineering, product, sales, and data-entry teams to learn the day-to-day work and find what could be automated.
  • Designed a DocuSign automation for commercial real estate partner onboarding. Each property used to need a manually created contract plus manual data entry into payment systems for ACH and card setup.
  • Identified the variable and static parts of every contract, built a templated DocuSign flow that auto-populates and routes to the right signers, then triggers automated data entry into the payment platform on completion.
  • Applied the same process-mapping method across multiple teams to surface and remove operational bottlenecks.

Impact

A multi-month, fully manual onboarding cycle dropped to three days end to end: contract generated, sent, signed, data entered, validated. It removed manually created contracts and dual data entry for an entire partner category.

DocuSign automationProcess mappingPayments integrationACH and card setup
VTechnical depth

AI tooling I have actually shipped, plus the projects that pushed into machine learning.

Model Context Protocol servers, a custom ML pipeline, and a database built at a granularity nobody else was tracking.

MCP

Remote MCP Server

Independent · Cloudflare Workers

A hosted Model Context Protocol server that hands any Claude client a set of authenticated, live tools over the network, with nothing to install locally.

nothing to installremote MCP, OAuth per user

What was built

  • Runs on Cloudflare Workers at the edge, so it is always on, scales on its own, and there is no server to patch or keep alive.
  • Full OAuth flow. Each person connects their own account, and the server only ever returns data that user is allowed to see.
  • Serves a live team leaderboard: the server pulls every member's current numbers, ranks them, and hands the standings back as structured data the model can reason over.
  • Typed tool schemas validated on every call, so the model gets a strict contract and bad input fails loudly instead of quietly returning nonsense.

Impact

Turns a normal chat window into something connected to live company data, with per-user permissions intact and no IT install on anyone's machine.

Model Context ProtocolCloudflare WorkersOAuthEdge runtime
XII

Local MCP Toolkit

Independent · 12 tools

A twelve-tool MCP server that runs on the machine and turns a desktop AI client into something that can actually operate the systems behind it.

12 toolsone desktop client, full reach

What was built

  • Twelve tools covering the reads, writes, and lookups I do daily, each one a single clear action instead of a catch-all.
  • Runs locally, so credentials and data never leave the machine and there is no third party sitting in the middle.
  • Every tool is described for the model in plain language, which is most of the real work. The difference between a tool that gets called correctly and one that gets misused is the description, not the code.
  • The pattern is portable. Once a business has an API, the tools that let an AI client drive it are a day of work, not a project.
Model Context ProtocolTypeScriptLocal toolingClaude
Lookzapp logo

Lookzapp

Independent · ML and Web

lookzapp.com

A consumer web app built on TensorFlow that maps 168 landmark points across a face in real time to compute structural metrics, then returns a scored analysis.

168facial landmark points, live

What was built

  • Trained and deployed a custom ML model for real-time facial landmark detection.
  • Built a real-time camera pipeline mapping 168 individual landmark points per frame.
  • Computed golden-ratio alignment, canthal tilt, and facial symmetry, returned as a scored analysis with supporting data.
TensorFlowCustom ML modelReal-time camera pipelineWeb
FightStats logo

FightStats

Independent · C# and .NET

A Windows desktop platform built to track UFC fights at a granularity that had never been done at scale, breaking every action into its specific form.

214 per fightvs. about 12 official metrics

What was built

  • Official UFC metrics track about 12 broad categories. FightStats breaks every action into its specific form: left hook to the body, right cross to the face, trip takedown, body-lock takedown.
  • Expanded tracked metrics to 214 per fight and built the most comprehensive UFC database available at the time: 168 fighters, 600 fights.
  • The advanced metrics from that dataset produced meaningful, verifiable results in predictive modeling.
C# and .NETCustom databasePredictive modelingDesktop
VIAI training

Train your team to actually use AI, not just search with it.

Most teams have an AI account and treat it like a smarter search box. I run hands-on sessions that turn it into a real part of how people work, built around the job your team already does. No technical background needed.

01Live, role-specific sessions built around the work your team already does, not generic demos.
02Prompting that holds up: context, roles, format, and chained prompts people will actually reuse.
03Skills, custom instructions, and agents, so the tool is tuned to each person's job.
04A shared prompt library for the whole team, plus a written reference guide after every session.
05Every session recorded and shared, so anyone can replay it at their own pace.
06Built for non-technical teams. If someone can write an email, they can do this.
Matthew took me from barely touching AI to using it in my day to day. He met me where I was, no technical background needed, and built everything around the work I actually do. I went from skeptical to having my own prompts and a workflow that stuck.

Brent Piepenbring

Soleo Health

View on LinkedIn
VIICurriculum development

Course material built with AI, reviewed by an engineer.

A different client than the automation work. Training organizations, technical schools, and manufacturers who need lab material produced faster than a subject matter expert can write it by hand.

Goes in

Bill of materialsComponent datasheetsCourse objectives

Comes out

Student lab manualGraded exercisesInstructor answer key
01A parts list and the component datasheets go in. A complete student manual comes out, written against the exact hardware in the kit.
02Real values pulled from the datasheets, so every exercise uses the components students are actually holding instead of generic placeholders.
03A matching instructor key for every exercise, so whoever teaches it is never solving problems live in front of the class.
04One consistent structure across the whole manual: objectives, procedure, data tables, and check questions in the same shape every time.
05Built to be revised. When the parts list changes, the manual gets regenerated instead of rewritten from scratch.
06AI does the drafting and I do the engineering review, so what ships is technically correct before a student ever sees it.
VIIIHow I work

How a build actually goes.

The same five steps on every engagement, so you always know what happens next and what it costs before it happens.

I

Discovery call

Thirty minutes on how the business actually runs. What the team touches by hand, what breaks, and what nobody has time to fix. No slides and no pitch deck.

II

Process mapping

I sit with the people doing the work and write down what actually happens, step by step. The real bottleneck is usually somewhere nobody flagged on the call.

III

Proposal with hours

A fixed scope. Every piece listed with the hours it takes and what it costs. You approve the number before anything gets built.

IV

Build with approval gates

Work ships in pieces and you sign off on each one. No multi-month black box, and no finding out at the end that it solves the wrong problem.

V

Handoff

You get the code, the accounts, and written documentation covering how it works, what it touches, and what to do when something looks wrong. It runs without me.

Optional

Then, if you want it, a retainer

Most clients keep me on a flat monthly retainer after handoff for monitoring, fixes, and small changes. It is optional, and everything is built so you are not stranded if you skip it.

IXQuestions I get asked

The things people ask before they hire me, answered once.

If yours is not here, text me at 716 263 2627 and I will answer it straight.

No, and it has never come up on a build. I get hired on what I have shipped, not on a badge. Everything in the work above runs in production for companies that depend on it daily, and you are welcome to talk to any of them. If your procurement process requires a certified vendor for a specific platform, tell me on the first call and I will tell you straight whether I am the right fit.

You own the code, the accounts, and the documentation from day one. Nothing runs on a login only I have, and nothing is hosted somewhere you cannot reach. Every build ships with a written handoff covering how it works, what it touches, and what to do when something looks wrong. Most clients also keep me on a monthly retainer, which means a break is my problem to fix, not a scramble for your team.

Yes, and it usually makes the build go faster. Your IT vendor owns the network, the devices, and the accounts. I own the automation and the data layer sitting on top of them. I get on a call with them at the start, we agree in writing on access and boundaries, and they stay in the loop on anything that touches their systems.

Fixed scope with an hours estimate, not an open-ended hourly bill. After the discovery call and process mapping you get a proposal listing exactly what gets built, the hours behind each piece, and the cost. You approve before anything starts. If the scope changes mid build, you get a new number before I touch it. You will never open a surprise invoice. Ongoing monitoring and small changes are a flat monthly retainer.

Most first builds land between two and six weeks from the discovery call, depending on how many systems have to talk to each other. You see working pieces at every approval gate along the way, so you are never waiting months to find out whether it does what you wanted.

That is the normal starting point, and sorting it out is most of the value. The discovery call and process mapping exist to answer exactly that question. I sit with the people doing the work, map what actually happens, and come back with a list of what is worth automating and what is honestly not.

XAbout

I learn how your business actually runs, then build the system it should run on.

I'm a -year-old technical architect and automation engineer in Buffalo, NY. I go into a business, learn how it actually runs day to day, and build the infrastructure that takes the manual, repetitive work off the team's plate.

Most businesses I work with are stuck maintaining instead of scaling. The data lives in a spreadsheet, the same numbers get keyed in twice, and the team spends its day keeping the lights on instead of growing. That is treading water. I replace it with systems that run themselves.

I also build custom dashboards designed around how you actually work, not a generic template. One place that shows the numbers that matter to your business, live, so decisions stop waiting on someone to update a sheet.

I have done this across fintech, moving and storage, vending, and SaaS, at companies ranging from early-stage startups to a publicly traded payments platform processing billions in volume.

Octavian Ideas is the studio that work runs through. It is me on every engagement, from the first call to the handoff, so nothing gets passed to a junior you never met.

FintechMoving and StorageVendingSaaSTechnical Education

Experience

Jun 2026 to Present

Co-Founder · Semres

Multi-tenant SaaS automation platform for the moving industry.

May 2026 to Present

Chief Technology Officer · Western New York Moving

Full back-end automation and operations infrastructure build-out.

Mar 2026 to Present

Technical Analyst · 4.0 Storage

Operations digitization and mobile workflow automation.

Jan 2026 to Present

Founder · Skyway Vending

Nightlife vending operator. Built internal ops and partner portals.

Jan 2025 to Present

CTO and Lead Technical Architect · Bracey Skyway Partners

Jan 2025 to Present

Freelance App and Web Developer · Self-Employed

iOS apps, web platforms, TypeScript.

May 2024 to Dec 2024

Technical Architect · Nuvei

Process automation and operational efficiency across business units.

Feb 2024 to May 2024

Intern · Nuvei

XIContact

Have a process that should run itself?

Tell me how your business actually works day to day, and I'll show you what can be automated away. You can call or text me, or grab a time below.

matt@braceyskyway.comCall or text · 716 263 2627LinkedIn

Book a call

Grab a time that works for you

Intro with Matthew Ryan