Most software purchases end with a login and a promise. You get access, not ownership. If you want a new field, a different report, or your own branding, you open a ticket and wait.
I wanted to sell the opposite: a complete Laravel codebase that a team can open in Cursor, Claude Code or Copilot and actually change.
What "complete" means
SuGuardia is a multi-tenant Laravel 12 platform for field operations and emergency alerts. The package I sell has:
- 682 source files and 133,610 readable lines;
- central and per-tenant migrations;
- Blade, Vite and Tailwind frontend assets;
- an offline-first PWA with IndexedDB sync;
- README, INSTALL, architecture and validation docs;
- no encoded or obfuscated code.
That last point matters more in the AI era than it did before. An AI assistant can only help with code it can read. A closed SaaS gives it nothing to work with.
What a buyer can ask an AI to change
A realistic prompt:
"Rename 'Guardia' to 'Operador' across the project, update views, permissions and PDF reports. Do not change the tenancy logic. Show me the diff and the tests."
That is not a magic one-click rewrite. It is a normal engineering workflow: the AI proposes a diff, a developer reviews it, runs the tests and deploys. But the starting point is a real codebase with migrations, policies and documentation, not a blank file.
Other examples:
- add a
severityfield to incidents (migration, request, view, PDF); - change the report layout for a client;
- integrate an ERP, CRM or local payment gateway;
- adapt roles and permissions to a different operation.
What I deliberately do not include
- support, SLA or consulting;
- installation, hosting or maintenance;
- customer data, credentials, APKs or third-party accounts;
- a monthly subscription.
It is a one-time commercial license for one implementation. The buyer's team installs it with the docs. That is the trade-off: lower price, more autonomy, no hand-holding.
The honest part
AI does not remove the need for engineers. It removes the "I have to rewrite this from scratch" tax. The buyer still needs someone who can review a diff, run migrations and test a deployment.
If you are evaluating a source-code purchase, ask for three things: the file count, the migrations, and a real README. If any of those are missing, you are probably buying a demo, not a codebase.
The landing page with the full breakdown is here: https://suguardia.appspesic.cl/codigo-ia.html
Disclosure: I'm the author and I sell this source-code license. No customers, revenue or production data are included.
Top comments (0)