Who delivers what, and when — clearly defined
TYS runs delivery through one integrated, human-verified model: a lean core team, supported by selected specialist partners depending on the task. Every deliverable has a single owner, and every output is human-reviewed before publication.
Few layers, clear ownership
No big-agency act. A small, direct structure means fast decisions and a clear point of accountability. Roles are defined as functions, not fixed headcount — one person can carry several functions, and some functions run with selected partners. No number is published without a source.
Accountability by function
Roles are functions, not fixed headcount. What matters: every function has a clear owner and a single point of accountability.
| Function | What it does | Who |
|---|---|---|
| SEO/GEO Strategy | Diagnosis interpretation, roadmap, prioritization | Core team |
| Technical Implementation | Schema/JSON-LD, sameAs, llms.txt, on-page fixes | Core team |
| Analysis & Reporting | AI Authority Score measurement, share of voice, monthly report | Core team |
| Specialist support | Content, design and development depending on the task | Selected partners |
| Final accountability | Quality sign-off, client decisions, crisis response | Founder |
Partner and freelancer support is not hidden; it is used transparently depending on the task — a sign of flexibility and honesty.
Only commitments we actually keep
These SLAs are defined and keepable; there are no invented “enterprise” figures.
Expert review within 24-48 hours of the measurement
A human-verified report every month + at least 1 concrete fix and 1 applied improvement
Baseline on Day 0, three monthly reports, decision gate on Day 90 (measured delta)
Four systems (ChatGPT, Gemini, Claude, DeepSeek), sourced and human-approved; no guarantee, no invented delta
Two-week monitoring cycle
The concrete rhythm of the monthly monitoring cycle and who takes part at each step.
| Time | Task | Who |
|---|---|---|
| Week 1 | Data collection (measurement across 4 systems, share of voice), draft report | Analysis function |
| End of week 1 | Human review of the draft (numbers and claims check) | Founder sign-off |
| Start of week 2 | The month’s concrete fix + applied improvement (schema/content) | Technical function |
| Week 2 | Report publication + short review (optional 20-30 min call) | Strategy function |
| Day 90 (in pilot) | Decision gate: measured delta from baseline to Day 90, continue/stop | Founder + Strategy |
The client takes part in the monthly report review and the Day 90 gate; large-team rituals are not invented.
Escalation and principles
Escalation path
- 1
Function owner — day-to-day work and delivery questions
- 2
Founder (Yılmaz Saraç) — quality sign-off, scope changes, crisis and final accountability
Every output is human-reviewed; the AI drafts, a human approves.
No number is published without a source; a target is set only after the baseline.
The number of concurrent active projects is capped; without capacity, no work is taken on.
Let’s talk about how we work
We’ll answer your questions about our delivery model and accountability structure.