What I can do
for your business.
Most businesses run on a spreadsheet somebody is afraid to touch, an Access database from 2009, six logins that do not talk to each other, and a person who knows how it all fits. I turn that into one system that does the work, connects to the services you already pay for, and belongs to you when I leave.
The way your business actually works, as software.
Every business has a workflow: a request comes in, somebody checks it, somebody schedules it, somebody does it, somebody bills it, somebody follows up. Off-the-shelf software makes you do it their way. A custom workflow app does it your way, and the parts that used to be re-typing, copying between tabs, and "let me check with Maria" become a screen that already knows.
I build these on a boring, durable stack (Laravel, PostgreSQL or MySQL, a plain web front end that works on a phone), with sign-in, permissions, backups and an audit trail from the first day. Then I wire it into the services you already use: take the payment in Stripe, post the invoice to QuickBooks, put the job on the calendar, send the customer a text when the truck is twenty minutes out.
Typical shapes: intake and approval flows, dispatch and scheduling, order processing, client portals, quoting and invoicing, inventory and purchasing, onboarding checklists, anything with a status that needs to move from one person's desk to another's.
A CRM is a workflow with a phone attached.
To me a CRM is just a workflow: who, what happened, what is next, by when, and who is responsible. It deserves its own callout because almost every business needs one and almost none of them fit what you can buy. The generic ones make your salespeople fill in forty fields to log one call, so they stop logging calls, so the CRM is wrong, so nobody trusts it.
I build CRMs around the way you actually sell: your pipeline stages, your follow-up rules, your lists. Dial queues that put the next call in front of the rep. Consent and do-not-contact rules built in, not bolted on. Mailing lists your office manager can build without asking a developer. Quotes that turn into orders that turn into invoices without re-keying.
I also run one. FireScout is a sales CRM I built and operate in production, with pipeline, dial queues and consent workflows. The same bones can be shaped to your process.
The Access database that runs the company, turned into something that can keep running it.
Microsoft Access was a fine way to build a business system in 2004, and a lot of good ones are still in use. The problem is not that they are old. It is that they live on one PC, break when two people open them, cannot be reached from a phone, and depend on one person who remembers why the query is called qryFinal2_NEW.
I convert them into proper multi-user web applications: your data moved into MySQL or PostgreSQL with its history intact, your forms rebuilt as screens that work in a browser and on a tablet, your reports preserved (the ones you actually use), and the parts that were manual now connected to the services around them. The same goes for the Excel workbook with macros, the FileMaker system, or the Google Sheet that quietly became your order book.
You keep working in the old system until the new one is proven side by side. Then you switch, and the old file goes in a drawer, not in the trash.
Data in, transform, data out.
This is the oldest kind of work I do and still the most valuable per hour. A report arrives from a vendor, a portal, a government system or your own ERP, in a shape nobody designed for you. Somebody spends a day a week turning it into what your system needs. I replace that day with a minute.
The example I keep coming back to: a federal contractor received CSV files that were actually several reports stacked in one file, with dates in European format in some sections and American in others. I wrote the piece that found the section boundaries, fixed the dates per section, merged the records and pushed them into their Microsoft ERP. A week of manual work became about a minute of input. Years later, after the company was acquired, the new owners called me back for a change request because the little tool still beat whatever had replaced it.
I do not need to have seen your ERP before. The skill is in taming inconsistent source data and getting it correctly into the target, and that does not change with the logo on the box.
The information is out there. Somebody is copying it by hand.
If a person in your office checks the same websites every morning and types what they find into a spreadsheet, that is a scraper with a salary. I build collectors that pull the data on a schedule, normalise it, flag what changed, and land it in a spreadsheet, a database or your own app, with the history kept so you can see trends instead of snapshots.
I do it properly: respecting the site's terms and robots rules, rate-limited so nobody notices you, using the official API where one exists, and avoiding personal data you have no business holding. If a source cannot be collected legitimately, I will tell you that instead of building something that stops working in a month.
Where the source is PDFs, scans or photos, AI document extraction turns them into rows. That is a job I have done a lot of lately, and it is far cheaper than it was two years ago.
The numbers you already have, answering the questions you actually ask.
Your accounting system, your CRM, your website, your point of sale and your spreadsheets each know a piece of the truth. Nobody can see all of it at once, so decisions get made on the piece that was easiest to find. I pull the pieces together into one place and build the reports and dashboards around the questions you ask every Monday: what did we sell, who owes us, what is late, which jobs make money and which just make noise.
That might be Power BI or Looker Studio on top of a clean data layer, scheduled reports that arrive by email before the morning meeting, or a page inside your own app. I learned Power BI while training someone else to use it, so I am comfortable teaching your people to drive it rather than making you call me for every new chart.
For anything quantitative beyond reporting (modelling, forecasting, custom calculation engines), I build the functions to your specification and document them so they can be checked. I once built a set of custom modelling functions for futures trading, delivered with the interface and documentation translated into Hebrew.
When the state wants a signed piece of paper and you want to stop keeping paper.
Schools, clinics, contractors, anyone billing a government program: there is a form you must keep, signed by hand, with times on it, and someone has to file it, find it, and produce it when the inspector comes. I build the electronic version that satisfies the rule and the inspector. Students or staff sign with a finger or a mouse, the system stamps the time, and the output looks exactly like the sheet the regulation describes.
The point is not the signature widget. It is that the record is complete, consistent and findable, and that the people filling it in need zero training because it looks like the form they already know.
AI where it earns its keep, and not where it does not.
Everything above can have AI in it, and most of it should not be AI-first. Where it pays: reading documents that used to be typed in, classifying and routing incoming requests, drafting the reply a human then approves, answering staff and customer questions from your own records, and agents that run a routine multi-step process end to end under supervision.
I run Fire, an inference API that routes to dozens of models with every call priced and logged, and FireControl, the operations layer that runs AI agents on this portfolio with an audit ledger, brokered credentials and a stop control. When AI goes into your workflow, that is what runs it, on a cloud you own.
And when an AI tool has already built you a prototype that now has to become a product, or a vendor's AI feature is running up a bill nobody can explain, I audit it, fix what is fixable and say plainly what is not.
The services I connect your workflow to.
If what you use is not on this list, it almost certainly has an API or an export, and I have never needed to have seen a system before to connect it.
Free call. Working session. Fixed price. Keys.
What I see and hear in your business stays in your business.
- Your books, your margins, your customer list, your mess. None of it leaves the room, from the first call on, whether or not you hire me.
- I do not name a client or describe their project without permission. Some of the work on this site says "name withheld" for exactly that reason.
- Your credentials never pass through an AI model, and your data never trains one.
- When we are done, I hand back every account and credential in your name and keep nothing I do not need to support you.
Want it in writing? Send me your NDA or use mine, signed before we talk specifics. It is in the terms too, section 6.
Tell me how your business runs today.
One reply: what I would build, what I would connect, and what it would cost.
