wojciech.io

Work

Built, shipped, and still running.

Selected work across GTM systems, AI tooling, and product delivery. Grouped by what it proves, not by when it happened.

Cluster 01

AI-native GTM systems

Practical AI implementation, workflow redesign, and code-assisted execution. Turning ideas into working operator tools.

AdsAI / Ad Assistant product screenshot
Ads intelligence
AIAdsGTM

AdsAI / Ad Assistant

An AI-native Google Ads cockpit: spend, ROAS, ICP fit, campaign priorities, and next-best actions in one workspace.

Problem
Ad optimization work was split between reports, intuition, and repeated checks.
System
Budget, ICP, ROAS, alerts, and actions are pulled into one decision loop.
Artifact
Live dashboard with campaign priorities and optimization queue.
View project
gtm-agent

$ claude run outbound

▸ read CLAUDE.md

▸ load ICP context

✓ score prospects

✓ draft sequence

cost: $3.40

CLAUDE.md
MCP tools
GTM skills
Agent repo
Claude CodeAIGTM

Claude Code GTM Agent Starter Pack

Open-source starter pack for building AI GTM agents with Claude Code. Designed for growth operators who want to ship AI-native workflows without starting from scratch.

Problem
Operators wanted AI-native GTM workflows but had no structured starting point — just blank Claude sessions and scattered prompt tips.
System
4-layer agent stack: CLAUDE.md operator identity → MCP tools → client memory files → 5 reusable operator skills. Covers research, enrichment, sequence drafting, and CRM updates.
Artifact
Open-source GitHub repo with full starter pack — CLAUDE.md template, skill definitions, folder structure, and MCP source.
View project
NotchCue product screenshot
macOS app
macOSSwiftCodex

NotchCue

A macOS teleprompter concept for calls, demos, and recordings. Keeps notes close to the camera so delivery stays natural.

Problem
Notes sit away from the camera, which breaks eye contact during calls and demos.
System
Prompts live around the MacBook notch with a focused reading surface.
Artifact
Product site and app concept built around the camera area.
View project

Cluster 02

Growth architecture in practice

Revenue-system thinking with real metrics, operating cadence, and growth levers. Built and run, not just scoped.

Cluster 03

Products actually shipped

Real product delivery with UX and conversion thinking. Proof of range beyond strategic documents.

Relora product screenshot
Operating system
AI workflowCRM-liteOps dashboard

Relora

A relationship operating system for local-government property teams. One place for contacts, owner context, communication status, and next actions.

Problem
Important owner conversations lived across inboxes, notes, and memory.
System
Contacts, relationships, briefs, status, and follow-up in one operator view.
Artifact
Live demo app with dashboard, relation map, and task flow.
View project
Camper Rental Booking Engine product screenshot
Booking flow
ProductBookingWeb app

Camper Rental Booking Engine

A self-serve camper rental site for browsing vehicles, checking dates, and moving from interest to reservation quickly.

Problem
Rental demand needed a clearer path from browsing to booking.
System
Inventory, dates, offer framing, and reservation CTA in one front-end flow.
Artifact
Responsive booking website with vehicle cards and search entry point.
View project
Product lab
ProductUtility appsAI

Działka+, Paczka+, Resume+

A cluster of focused utility apps shipped independently: a plot management tool, a parcel tracking aggregator, and an AI-assisted resume builder. Each solves one real problem, ships fast, and proves range beyond strategic documents.

Problem
Recurring operational gaps that SaaS subscriptions were too heavy to fill — each problem needed a focused tool, not a platform.
System
Individual apps designed around one job-to-be-done each. Built with AI-assisted development, deployed independently, and running in production.
Artifact
Live apps available at app.wojciech.io/apps — plot management, parcel aggregation, AI resume builder.
View project

Next step

Have a system worth fixing?

Send the context, the current bottleneck, and what already exists. I will tell you where I would start.