Mockup to production: finish the app you built with AI

Your own domain pointed at the app, with HTTPS, and your existing email still working afterward.

Builder tools publish your app at an address on their domain, not yours. I point your own domain at the real host and set up HTTPS. Before changing any DNS, I write down the records you already have, especially the MX records that deliver your email, so moving the website doesn't quietly break your inbox.

Send and receive through Google Workspace or Microsoft 365, with SPF, DKIM, and DMARC set up so mail lands in inboxes, not spam.

Those three records tell other mail servers that your app is allowed to send as your domain. Without them, password resets and order confirmations land in spam or get rejected. If the app sends a lot of mail, such as receipts, notifications, or newsletters, I set up a transactional email service built for that volume, under your domain and your account.

Leads, contacts, and orders flow into HubSpot, Salesforce, Zoho, or whatever you already use.

That includes Pipedrive and other CRMs with an API. I connect the app through the CRM's API or its webhooks, so a new lead or order shows up where your team already works, and nobody types the same contact into two places.

Hosting sized to the job, in your name and on your billing.

A small internal tool doesn't need what a busy storefront does, and the bill should reflect that. The account is yours from day one, so keeping the app online never depends on me or on a builder tool's plan.

Real accounts and roles instead of a shared link.

Staff, customers, and admins each see what they should and nothing more. Where it fits, people sign in with the Google or Microsoft account they already have, so there's one less password, and switching off someone's work account switches off their access too.

API keys out of the code, the database locked down, customer data handled properly.

Prototypes built quickly tend to skip the same things. I check for them:

• Secrets. API keys and passwords out of the repository, and out of the code that ships to the browser, where anyone can read them.
• Database access rules, such as Supabase row-level security, so one customer can't read another customer's records.
• Input validation. Everything a user sends is checked on the server, not just in the form.
• Dependencies. The packages the app is built on, checked for known vulnerabilities.

Backups, monitoring, and a written runbook, plus ongoing support if you want it.

• Backups of the database, with a test restore to prove they work.
• Uptime monitoring, so you hear the site is down before a customer tells you.
• Error reporting, so a crash arrives with enough detail to fix it.
• A written runbook: how to deploy, how to restore from a backup, and where every account lives.

You do. The code lives in your GitHub account, and every account the app depends on, from the domain and hosting to the email and the database, is in your name and on your billing.

If we stop working together, nothing has to be handed back, because none of it was ever mine.

With a free review of what you have. I look at the app, the code, and the accounts behind it, and tell you what works, what's risky, and what's missing.

Then you get a fixed quote to finish it, so the price is settled before the work starts. Sometimes rebuilding a piece costs less than patching it; when that's the case, I'll tell you.

I use AI coding tools every day too. The difference is 30 years of writing, reviewing, and running production software, including engineering and management at Microsoft and Yahoo, so every line that ships has been read and tested.

I'm based in Manchester, NH. Software work doesn't need me on site, so I work with clients anywhere.