SiteKapında

Inspiration

Many local businesses in Türkiye still depend on social media, messaging apps, or map listings because building a professional website can feel expensive, technical, and risky.

But these businesses do not begin with a website brief. They begin with a harder question:

Who can I trust to build it?

SiteKapında means “your website at your doorstep” in Turkish. We reversed the usual website sales process:

Do not sell the promise. Bring the first version.

Our goal is to let a business see something tailored and tangible before committing—while keeping the owner in control of every decision that can affect their brand, money, or public presence.

What it does

SiteKapında is a human-supervised workflow that discovers businesses without strong websites, creates a business-specific first version, manages the sales conversation, and carries an approved website toward launch.

The end-to-end flow has eight stages:

Discover

Account-local Codex automation experiments, configured with GPT-5.6 Sol and an hourly schedule, inspect permitted public sources. They verify the missing-website signal, collect public business contact channels, reject low-confidence cases, and save only evidence-backed opportunities.

Create a tailored first version with GPT Image

Business facts and image rights are handled separately. When visuals are licensed, owner-supplied, synthetic, or explicitly authorized, GPT Image can preserve the real venue or products while rebuilding the imagery for a professional website.

The project demonstrates distinct directions for restaurants, beauty businesses, dental practices, cafés, automotive services, fitness studios, florists, pet groomers, education providers, and other local-business categories.

Save everything in the Sales Ops panel

Qualified leads enter the SiteKapında panel with:

Source and qualification context
Public contact channels
Desktop and mobile website concepts
Opportunity score and rationale
Sales notes and next actions
Contacted, Interested, Not interested, Approved, and Do not contact states

The salesperson sees the reason to believe, the proposed first version, and the current relationship state in one place.

Contact transparently

A human sales operator reviews the lead and the proposed design before contacting the business. Concepts remain private, are never presented as an official website, and are never published automatically.

The owner can decline, request no further contact, express interest, or continue to a working demo.

Show a working demo through Codex Sites

When a lead is interested, the demonstrated Codex Sites workflow produces a live private demo—not the final public website.

The customer opens a Sites link and can request specific changes to:

Copy
Imagery
Layout
Services
Calls to action
Mobile presentation

Revise and approve

Codex continues from the same customer context until the owner explicitly approves the version that may be released.

Human approval is required before publication. The workflow does not treat silence or initial interest as permission to launch.

Register the domain and go live

After the Sites version is approved, the demonstrated release workflow preserves that exact version.

With explicit purchase confirmation, a Cloudflare integration can check and register the custom domain and apply the required DNS records. Domain purchase, DNS changes, and deployment are separate, human-authorized actions and are disabled in the judge quick-start.

Keep a persistent customer developer

Each customer can retain a persistent Codex task containing the website’s decisions and development history. The same context can support later bug fixes, copy changes, new sections, and product improvements instead of starting from zero with a new developer.

In the future, this context can be packaged as a customer-owned Codex skill so the business owner can continue improving the website with their own agent.

How we built it

We built SiteKapında as two connected layers.

1. A portable, judge-ready application core

The submitted repository contains a deterministic Python and SQLite pipeline for:

Candidate normalization
Deduplication
Compliance and category rejection
Website-strength classification
Opportunity scoring
Lead persistence
Sales lifecycle states
Reports
Sales Ops workspace generation

The default judge path uses twelve fictional businesses and makes no network requests. It does not require an OpenAI API key, Google API key, Cloudflare credentials, or production customer records.

The repository includes:

Twelve fictional business examples
Twenty-four GPT Image website UI mockups
Twelve independent desktop designs
Twelve independently composed mobile designs
A searchable English Sales Ops panel
Nineteen offline tests
A one-command bootstrap
Five reusable SiteKapında Codex workflow skills

2. A Codex-assisted production workflow

During Build Week, GPT-5.6-class models in Codex—primarily the gpt-5.6-sol profile—helped us:

Research and understand the original project
Improve discovery-agent prompts
Strengthen rejection and qualification rules
Add image-rights safeguards
Create distinct design directions
Develop and test the Sales Ops interface
Build responsive website examples
Review safety and release gates
Produce the Remotion demonstration video
Package the project as a clean GitHub repository for judges

The demonstrated discovery configurations use:

model = "gpt-5.6-sol"
schedule = "hourly"
reasoning = "xhigh"
source_policy = "permitted_public"

These scheduled Codex experiments remain paused in the submitted package. The offline Python application does not hide an autonomous GPT-5.6 API runtime.

GPT Image was used during the authoring workflow to create rights-safe, business-specific visual directions. The offline runtime presents the resulting local assets but does not regenerate them.

Codex Sites demonstrates the private review stage through a working hosted example:

Open the Codex Sites demo

Cloudflare domain registration and DNS deployment are represented as separately authorized release steps rather than automatic judge-path actions.

Challenges we faced

The hardest challenge was not generating a website. It was building an agentic workflow that remains useful without becoming misleading or unsafe.

Consent and identity

A generated concept must never be presented as the official website of a business. Private concepts, outreach, approval, purchasing, and publication require different controls.

Image and brand rights

A public image is not automatically reusable. We separated business facts from image rights and restricted the visual workflow to synthetic, licensed, owner-supplied, or explicitly authorized material.

Preventing invented claims

Website designs can easily introduce fictional reviews, awards, prices, statistics, or guarantees. Our prompts and review rules explicitly reject those additions.

Combining many workflows

Discovery, qualification, image generation, sales operations, responsive development, revisions, domain registration, and maintenance all require different tools and approval boundaries.

Portability

Codex tasks and schedules belong to the creator’s environment. We therefore packaged the transferable parts as:

AGENTS.md repository guidance
Reusable Codex skills
Versioned prompts
Transparent automation examples
An offline deterministic runtime

Judges can clone the repository, open it in Codex, and reproduce the safe synthetic workflow without our credentials or account state.

Accomplishments that we are proud of

We are proud that SiteKapında became more than a concept deck.

We built a working Sales Ops product, a reproducible discovery and qualification pipeline, twelve sector-specific examples, twenty-four desktop/mobile GPT Image designs, a Codex Sites review experience, reusable Codex skills, and a GitHub-ready judge package.

We also tested the central business assumption manually.

In a founder-reported pilot of ten businesses:

Four liked the design direction, but the conversations stalled
Five said they were not interested
One became the first paying customer

The panel preserves all three outcomes—Contacted, Interested, and Not interested—because failed conversations are product evidence, not vanity-metric failures.

Çağrı Karakaş became the first customer implementation: a polished, responsive personal-training website running on its own domain.

Visit cagrikarakas.com

This was important proof that the workflow could move beyond a generated concept and become a real customer website.

What we learned

We learned that the most useful AI system is not always the one with the fewest humans.

For business identity, communication, payments, domains, and publication, the stronger design is:

Agents do the repetitive work. Humans make the consequential decisions.

We also learned that showing a tailored first version creates a very different conversation from selling an abstract website service.

The visual concept helps the owner react to something concrete. Codex Sites turns that reaction into revision requests. Persistent Codex history then transforms a one-time website build into an ongoing developer relationship.

Finally, we learned that negative outcomes matter. Recording why a lead declined or why a conversation stalled helps improve discovery, qualification, design direction, and outreach.

What’s next for SiteKapında

Our next steps are to:

Harden the paused Codex automation experiments into monitored production workflows
Add auditable consent and image-rights records
Connect approved CRM and messaging channels
Build a secure customer review and approval portal
Expand industry-specific design systems
Support Turkish and English website generation
Improve qualification using real sales outcomes
Add owner-approved domain, analytics, SEO, and maintenance workflows
Preserve customer context across long-term fixes and new features
Package customer histories as owner-controlled Codex skills
Expand from Türkiye market by market