You built an app with AI. Now a customer wants to know it’s safe.
Your field has technical rules for handling client records. I get your app ready to meet them, running on cloud accounts in your name. Then I hand you the written evidence, so you have an answer ready for whoever asks.
HIPAA for health records, the FTC Safeguards Rule for financial and tax data, and their equivalents in law and insurance.
I'll tell you what I'd fix first in what you've built, and why. No pitch.
If your app holds records the law protects, the platform you built on will tell you the same thing I do: move it to cloud accounts in your name, set up by a developer. Why not the hosting that came with your tool? →
Want to see what you end up with? Read a real handover document →
Who I help - How I can help
Most people I work with built their app with an AI tool. They usually arrive for one of two reasons.
Either you work in a field with rules about handling client records. You are a therapist, an advisor, an accountant, or an attorney, and the information your app holds is the kind the law protects.
Or you have a deal on the line, and a customer or an investor has just asked where your data is kept and who can reach it.
Either way, it is no longer enough that the app works when you demonstrate it. Someone is going to check it, and it has to hold up. That is the work I do.
Compliance-Ready Deployment - In a regulated field? Your app has rules to meet.
If your app handles protected data, there are technical rules it has to meet before a customer or a partner will trust it. The tool you built with does not know those rules apply to you.
What getting ready involves
I work through your app against the rules your field imposes, fix what does not meet them, and write down what was done. The written record is the part you can hand to whoever asks.
- A written check of your app against the technical rules your field has to meet
- Your data encrypted — scrambled so it cannot be read even if someone takes a copy — both where it is stored and while it travels
- A second step at sign-in for your staff, and access limited to what each person actually needs
- A record of who reached what, a daily check that the app is up, and backups restored at least once to prove they work
- The data-protection agreement your cloud provider has to sign, arranged and filed
- A written guide your team can follow, and evidence of every setting that was changed
What I do
I configure your app and the cloud it runs on to meet the technical rules, then produce the written evidence that it was done. That is the part that needs an engineer, and it is the part most owners cannot do themselves.
What stays yours
Being ready to meet the rules is not only a technical question. Your written policies, staff training, the person you name as responsible, your ongoing review of what could go wrong, and the statement you sign all stay with you. I tell you plainly which is which, in writing, before we start.
A fair question - Why not just use the hosting that came with your AI tool?
For a lot of apps you should, and I will tell you so on the call.
The hosting built into these tools is good. It is one button, it costs very little, and it means you never have to think about servers. If your app does not hold records the law protects, it may be all you ever need.
Protected records change the question. Your provider has to sign a data-protection agreement. You have to say where the records are kept and who can reach them. When a customer security review arrives, you have to produce evidence. Those are answers about the account your app runs in, not about your app.
This is not only my view: it is where the platforms’ own guidance sends an owner with rules to meet. Needing to move does not mean you did anything wrong. It means your app now holds something that has rules attached to it.
I'll tell you what I'd fix first in what you've built, and why. No pitch.
What AI tools leave you to solve - Built something with AI? Here's where most people get stuck.
AI tools now let almost anyone build a working application. Nearly everyone gets stuck at the same point, and it is rarely the code that stops them.
Your app isn’t secured
Apps built this way commonly ship with passwords written into the code, and with nothing stopping someone guessing at your sign-in page over and over. The settings are fine while you are testing and dangerous once real customers arrive. These are the first things a customer’s security review looks for.
Anyone could log in as anyone
Getting a sign-in page working is easy. Making sure each person can only ever reach their own records, and being able to prove it to a regulator, is a much harder job that AI tools rarely finish.
You don’t control the infrastructure
If your app runs on the AI tool’s own hosting, a pricing change or a closed account can take it offline and you have no say. Running it on cloud accounts in your name means the app, the data, and the bill are yours, and you can answer where your data is kept.
Your field has rules your app has to meet
If your app touches health records, financial data, or legal matters, it is not just a website. There are technical rules it has to meet, and customers and investors increasingly ask how you meet them. An AI tool has no idea those rules apply to you. I build with them in mind from the start.
Getting it live is harder than it looks
Pressing “deploy” in an AI tool puts something on the internet. It does not give you backups, a way to undo a bad change, or any warning when the app stops working. Those are separate jobs, and the tool will not mention them.
AI can build the app. It cannot tell you what it will cost to run each month, whether your customers’ data is safe, or what happens the day it goes down.
I'll tell you what I'd fix first in what you've built, and why. No pitch.
Services - Get your app online, and keep it there.
Two ways to get deployed, and one way to stay that way. The two deployments do the same engineering; the higher tier adds the written record that the rules were met, which is what a client in a regulated field is paying for. You get a fixed quote before any work starts.
Secure Cloud Deployment
Get your app online
From $2,500
For an app that does not hold protected records. I move it onto proper cloud hosting: set up correctly, secured, backed up, and watched so you hear about problems before your customers do.
- Your app reviewed for security issues before anything goes live
- Everything your app runs on is written down as it is built, so the whole setup can be rebuilt exactly
- Login and access controls configured so only the right people get in
- Future updates go live by themselves, so a change never depends on someone remembering the right steps
- A written handover covering every account, password, and security setting. See example →
Compliance-Ready Deployment
Regulated-data readiness
From $6,000
For an app that holds health records, financial and tax data, or legal matters. Everything in a Secure Cloud Deployment, plus the work and the written evidence the rules of your field ask for.
- Everything in a Secure Cloud Deployment
- A written check of your app against the technical rules your field has to meet
- Evidence that your data is scrambled where it is stored and while it travels
- A record of who can reach what, and who actually did
- The data-protection agreement your cloud provider has to sign, arranged and filed
- All of that evidence collected into one document, and a plain list of what stays your responsibility
Keep your app running
Ongoing support
Contact for a quote
After the deployment. Keeping a live app healthy is its own job, and the rules of your field do not stop applying the day it goes live. I already know how your app is put together, so none of it starts from scratch.
- Your live app kept secure and up to date
- Up to 10 hours a month of changes and improvements to the app I deployed
- The daily check and monthly report included, at no extra charge
- A regular look at your hosting bill, so you are not paying for capacity you never use
A daily check on your app
Ongoing support
$49/month
An insurance policy for an app that is already live. I keep an eye on it, you get a written report once a month, and anything I find is priced before anything is done.
- Checked every day that it is up and responding, so you hear about a problem before your customers do
- A written report each month in plain language, and a quiet month says so
- Evidence the checks ran, for a customer security review or an insurer
- The first two months free, and you can stop at the end of any month
How getting your app online works - Simple, clear, no surprises.
Four steps from your first message to a live, secured app. The first one is free. The other three are the three milestones, one each, and you approve every one before the next begins.
Tell me about your app
Book the free review, or send me a message about what you’ve built and what you need. You don’t need to know any technical detail to answer. You leave this step with a fixed quote and nothing owed.
I review what you have
The first milestone. I go through your app properly and write down what has to happen before it can go online safely, what it will cost to run, and how long it will take. Plain language, and yours to approve.
I get it deployed and secured
The second milestone. I build the hosting, secure the app, and set up who can get in. You try it on a private test address only you and I can see, and approve it before anything goes live.
You get the keys
The third milestone. Your app goes live, and I hand over a written record of every account, password, and security setting, plus a walkthrough of what was done.
A recent project - What this looks like in practice.
The owner of a solo consulting practice came to me with an app they had built with an AI coding tool. It worked, but it was not ready for the questions that arrive with real customers. I read through all of it, told them what I found, and rebuilt how it runs: who can sign in, what each person can reach, and where the data sits. At the end they had a written record their own team could work from, without calling me for every question.
I finally feel like I actually own my app.
How your work is delivered - Your documentation lives somewhere you can find it.
Nothing important arrives as an email attachment you have to search for later. Your quote, your evidence, and your handover live in a private client area you reach from a link. There is no account to create and no password to remember.
Shown with an invented project. Real client pages are private and are not listed in search engines.
An engineer who starts from your business, not the code.
I’m Will, a software engineer with an MBA from The Ohio State University. I’ve spent my career building software that the person running the business can operate, not just software that satisfies the engineer who wrote it. A project has gone well when it solves your problem, not when the code runs.
Learn more about meTwenty minutes, and no pitch.
I'll tell you what I'd fix first in what you've built, and why. No pitch.