01
Intake and bookings
The form is where most small businesses lose the sale. We build intake that survives a weak signal, confirms in writing, and lands in an admin screen somebody will actually open.
Already built
- ·Café reservation system with table availability
- ·Invite-only membership intake for a tournament
- ·Competition video submission portal
- ·Raffle entry with qualifying questions
- ·Digital contact card with lead capture
02
WhatsApp operations
Here the business already lives in a chat thread. Instead of moving customers off it, we put structure behind it: orders, payments, and a record of what was promised.
Already built
- ·Chat threads turned into structured orders and customers
- ·Payment record manager for a service business
- ·Automated replies bound to a written company truth base
03
Storefronts and commerce plumbing
A store is the easy half. The hard half is the product feed, the local inventory, the tax and shipping edge cases, and knowing which channel actually sold the thing.
Already built
- ·Bilingual headless storefront on puntopio.com
- ·Google Merchant and Meta catalog feeds, kept in sync
- ·Self-hosted WooCommerce analytics, built to replace a paid tool
- ·Custom local payment gateway plugin
04
Brand sites that convert
For businesses running on Instagram alone. One site they own, in Spanish and English, pointed at a single action: a booking, a call, or an order.
Already built
- ·Restaurant menu and ordering site
- ·Coworking ecosystem brand site
- ·Mural studio site built around discovery-call bookings
- ·Membership club site with an application flow
05
Research and monitoring pipelines
Agents that go and find out, then hand back something a person can decide on. Local-first where the data is sensitive, and always with the unverified parts marked as unverified.
Already built
- ·Competitor and creator research briefs
- ·Lead lists built and qualified for a narrow vertical
- ·Automated site performance and SEO auditing
06
Agent operations
If a team is going to run coding agents, somebody has to make them accountable. Shared skills so every machine follows the same playbook, credentials that are never printed, cost visibility, and a kill switch for the day a deployment runs away.
Already built
- ·One skill library synced across Claude Code, Gemini, Cursor and Kilo
- ·Secrets referenced by path, never by value
- ·Deployment kill switch with an append-only audit log
- ·Self-hosted Supabase and Caddy behind a private tailnet
07
Proposals and sponsorship decks
Written from the asking side, which is the harder side. We research what the other party actually needs, put the numbers where they can be checked, and mark every figure we could not verify instead of rounding it into a claim.
Already built
- ·In-kind activation proposals to national brands
- ·Festival and tournament sponsorship packages
- ·Legislative advocacy dossier for an agricultural initiative
- ·Subscriber renewal campaign copy, tested before sending
- ·On-site quoting from a phone measurement, straight to PDF