SiteKapında

What the company appears to be: SiteKapinda is a self-reported human-supervised AI workflow for discovering local businesses without websites, creating tailored first versions of their websites using GPT Image and Codex agents, and managing the sales process through a dedicated panel before launch. The system uses automation for discovery and content generation but requires human approval at every step.

What changed: The project evolved from an idea to a working prototype that includes a deterministic offline Python application, a set of reusable Codex skills, and a demonstration of how the workflow would function in production with human oversight.

Single most important open question: Is there sufficient evidence of traction or early customer adoption beyond the author's own pilot with ten businesses, including one paying customer?

Note: This analysis is based entirely on the self-reported description provided by the author. No external verification or independent data is available. All claims are treated as stated by the author and not proven facts.

The description states that SiteKapinda is a human-supervised workflow designed to:

• Discover businesses without strong websites
• Create tailored first versions using GPT Image
• Manage sales conversations through a panel
• Carry approved websites toward launch

It includes an eight-stage process involving:

1. Discovery via Codex automation
2. Creation of business-specific website concepts with GPT Image
3. Saving leads in a Sales Ops panel
4. Contacting businesses transparently (with human review)
5. Showing working demos through Codex Sites
6. Registering domains and going live with Cloudflare integration
7. Keeping persistent customer developers for future edits

The system is built as two connected layers:

1. A portable, judge-ready application core using Python and SQLite
2. A Codex-assisted production workflow using GPT-5.6 Sol models

Claim: SiteKapinda uses Codex agents and GPT Image to find businesses without websites and bring them a tailored first version before the sales pitch.

Evidence: The project description explicitly states this.

Inference: The system is designed to be human-controlled throughout, with no autonomous publishing or automated launches.

Evidence: The description says "Humans approve every launch" and "Human approval is required before publication."

The author positions SiteKapinda as a solution to the problem of local businesses in Turkey lacking professional websites due to cost, complexity, or risk. It reverses the typical sales process by bringing a tangible first version rather than selling promises.

Key claims:

• "SiteKapinda 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"

The project evolved from concept to prototype, including:

• A working Sales Ops product
• Twelve sector-specific examples
• Twenty-four GPT Image designs
• Codex Sites review experience
• Reusable Codex skills

Claim: SiteKapinda aims to help local businesses get websites and show how AI agents can work together as a human-controlled digital production team.

Evidence: The author states this in both the "What we learned" and "What’s next for SiteKapinda" sections.

The description indicates that SiteKapinda targets local businesses in Turkey that currently rely on social media, messaging apps, or map listings because building a website feels expensive, technical, or risky.

These businesses are described as:

• Not starting with a website brief
• Beginning with the question: "Who can I trust to build it?"
• Likely to be in categories such as restaurants, beauty businesses, dental practices, cafés, automotive services, fitness studios, florists, pet groomers, education providers, etc.

Claim: Local businesses without websites in Turkey.

Evidence: The description explicitly identifies this group as the target audience.

Inference: The ICP likely includes small business owners who are hesitant to commit to website development due to perceived complexity or cost.

Evidence: The author states that these businesses depend on social media or map listings and find traditional website-building processes intimidating.

There is no explicit mention of pricing, revenue models, or monetization strategies in the provided description.

The only reference to payment comes from a founder-reported pilot:

• One out of ten businesses became the first paying customer
• The author mentions a "first customer implementation" (cagrikarakas.com)

Claim: There is no stated business model or pricing structure.

Evidence: No pricing, revenue, or monetization details are included in the description.

The system uses:

• Codex agents with GPT-5.6 Sol
• GPT Image for visual generation
• Cloudflare for domain registration and DNS changes
• Python and SQLite for offline deterministic pipelines
• React, Next.js, Tailwind, FastAPI, Node.js, TypeScript, HTML/CSS

The project includes:

• Twelve fictional business examples
• Twenty-four GPT Image UI mockups
• Twelve independent desktop designs
• Twelve independently composed mobile designs
• A searchable English Sales Ops panel
• Nineteen offline tests
• Five reusable Codex workflow skills

Claim: The system uses Codex agents and GPT Image to automate discovery and content creation.

Evidence: The description states this clearly.

Inference: The system is designed to be portable and reproducible without external credentials.

Evidence: The author says judges can clone the repository, open it in Codex, and reproduce the workflow without access to their credentials or account state.

The description reports:

• A founder-reported pilot of ten businesses
  • Four liked the design direction but conversations stalled
  • Five said they were not interested
  • One became the first paying customer
• The demonstration includes a live example (cagrikarakas.com)
• Twelve sector-specific examples and twenty-four GPT Image designs

Claim: There is limited traction beyond a pilot.

Evidence: Only one paying customer is mentioned, and no revenue or customer data beyond this is provided.

Inference: The project has moved from concept to prototype but lacks measurable market adoption.

Evidence: The description does not include any metrics on user growth, retention, or sales volume.

The description does not provide information about competitors or the competitive landscape. It focuses solely on describing SiteKapinda’s own functionality and workflow.

Claim: No competitive context is provided.

Evidence: The document contains no references to existing players in the local business website-building space.

• Lack of verified traction or revenue: Only one paying customer reported in a small pilot.
• Unproven scalability: The system appears designed for human supervision and may not scale efficiently without significant additional resources.
• Dependency on human approval at every stage: This could limit speed and efficiency, especially if the goal is mass adoption.
• No clear monetization path beyond early pilots: No pricing or business model details are provided.
• Limited market expansion strategy: The vision mentions expanding "market by market" but no concrete plans for scaling beyond Turkey.

Inference: Without independent verification of traction or a scalable business model, the risk of failure is high.

Evidence: The description lacks any data on customer acquisition costs, conversion rates, or long-term viability.

1. What specific metrics do you use to evaluate success in your pilot?
2. How do you plan to scale this workflow beyond a single-person operation?
3. Can you provide more details about the one paying customer? Was it a one-time deal or part of a recurring model?
4. Are there any legal or compliance issues related to image rights or consent that have emerged during development?
5. What are your plans for integrating CRM and messaging systems into the workflow?
6. How do you intend to expand beyond Turkey, and what cultural adaptations will be needed?