What You Own

Two questions every buyer asks before signing: what do I own when this is finished, and what happens if the work stops. Here are the honest answers, with the proof.

What you own

What you own when the work is done

Every engagement runs on a Work Made for Hire clause, not a license. Nothing is rented back to you.

The code and the repository

From the first line of code, the repository belongs to you. Every service page states the same clause: once you pay, the code is one hundred percent yours, and I keep nothing.

The cloud accounts

The cloud accounts that run your product belong to you, not to me. I build to hand off, so you keep total control and independence, with no vendor lock-in.

The documentation

Every build includes a handover: documentation, comments, and a walkthrough, not only a code drop. A future developer, including one who is not me, can pick up the project from what you receive.

The design and the content

Design files, written content, and every asset created for the project transfer to you at final payment, alongside the code.

Service by service

How this plays out, service by service

Websites
Hosting is set up for you at launch. The ongoing bill goes straight to your hosting provider, not through me. Once you pay, the site, the design, and the content are completely yours.
MVP Development
At launch, you receive the source code, the cloud account, and your own domain, plus a short walkthrough. Everything transfers the moment final payment clears.
Custom Web Applications
Code, architecture, and every deliverable belong to you the moment you pay. Documentation and comments ship with every change, so a handover is never a scramble.
AI Development
All code, prompts, and infrastructure belong to you. I keep no copy of anything I build for your product.
Fractional CTO
This is advisory and leadership work. I never need production data access, so there is no system access to hand back, only documents, decisions, and frameworks, all already yours.
HubSpot Integrations
Everything runs inside your own accounts. The sync control panel stays in your HubSpot portal. I keep no copy and no standing access once the work is delivered.
If the work stops

What happens if the work stops, or you can't reach me

Ownership starts on day one, not on exit. Here is what that means in practice.

Ownership never waits for an ending

The repository and the cloud accounts are already yours once you pay, not something you receive only if the relationship ends. The project keeps running on infrastructure you already control.

Cancel any time, no lock-in

Custom Web Applications, AI Development, and Fractional CTO are all billed month to month. Cancel any time, no notice required, no penalty.

A fourteen-day guarantee on every engagement

Every paid engagement starts with a fourteen-day money-back guarantee. Not happy in the first two weeks, full refund, no questions asked.

A named handover, not a vague promise

At the end of a Fractional CTO engagement, you keep every document, architecture decision, and framework produced, and I help you onboard a full-time replacement if you hire one. On an MVP, you can take the code and leave, or move to an ongoing subscription. Either way, the handover is documented, not improvised.

Seventeen years, no disappearing act

I have built software since 2009. You get daily updates, clear timelines, and a direct line to me, not an account manager. My customers stay for years, not months.

Questions about ownership

Common questions before you sign.

You do. One hundred percent. From the first line of code, the repository, the cloud accounts, and the assets belong to you. I build to hand off, ensuring you have total control and independence, with no vendor lock-in.

For HubSpot integration work, no. I keep no copy and no standing access once you pay. For Fractional CTO work, I never needed production access in the first place.

Cancel any time. Custom Web Applications, AI Development, and Fractional CTO are all month to month, with no penalty and no notice required.

The same things you already own: the repository, the documentation, and the cloud accounts. There is no separate export step, because nothing was ever locked away from you.