LAYER-01
Clarify the decision and architecture
If the idea, reference product, scope or production path is still unclear, we lock what should happen first.
SIGNAL · REVERSE · FORGE · SHIP
Türkiye / from 4,500 TLInspect scope
SRV-INDEXSERVICESPRODUCT / SYSTEM / OPERATIONS
Do not guess which service you need.
We first establish the problem and evidence level, then move through DISCOVER → STRUCTURE → DESIGN + BUILD → LAUNCH → LEARN from the point the product actually needs. Product Diagnostic chooses the intervention route.
ONE PRODUCT LOOP01 → 02 → 03 → 04 → 05 ↻
01
DISCOVER
SIGNAL · REVERSE
02
STRUCTURE
FORGE
03
DESIGN + BUILD
BUILD
04
LAUNCH
SHIP
05
LEARN
OPERATE · SIGNAL
AFTER DIAGNOSIS
Three intervention layers. Diagnosis chooses the right one.
These are not competing packages. Use this section to inspect what each post-diagnosis scope contains and the commercial frame it operates within.
LAYER-02
Build or rescue the product
If scope is clear, we implement it; if a live system is fragile, we stabilize the critical technical issues.
BUILD · RESCUE
Scope-basedInspect scope
LAYER-03
Operate the live product
If release, maintenance, monitoring and technical ownership need to run continuously, we take on operations.
OPERATE
Türkiye / from 9,500 TL / monthInspect scope
/ 01
DECISION & ARCHITECTURE
Close the right question before code.
The four systems are not competing packages. Only the one matching the current uncertainty needs to run.
SIGNAL / SYS-01
Opportunity pre-validation
Before code, gathers public demand, competition, complaint, pricing and whitespace signals; separates them from first-party customer evidence and returns BUILD / MODIFY / STOP + confidence + the next customer test.
INPUT
Idea + target user + any customer evidence
OUTPUT
Decision matrix + evidence boundary + next test
REVERSE / SYS-02
Product reverse analysis
Decomposes a reference product into observed behavior, flows, information architecture and system hypotheses, separating transferable principles from patterns to avoid.
INPUT
Reference product + analysis intent
OUTPUT
Evidence log + principle map
FORGE / SYS-03
Product architecture
Combines evidence from SIGNAL, REVERSE or equivalent sources with goals and constraints; classifies evidence confidence first, then turns product decisions, flows, architecture and acceptance criteria into a build contract appropriate to that evidence level.
INPUT
Evidence + evidence confidence + goal + constraints
OUTPUT
Evidence-bounded build contract
SHIP / SYS-04
Production readiness
Moves a working prototype through technical release gates while also locking the measurement plan and real baseline metric; security, data, performance, observability and deployment can be green without granting GO to an unmeasurable launch. Rescue of an already-live broken product belongs to RESCUE.
INPUT
Repository + working prototype + measurement plan + real baseline metric
OUTPUT
Technical release gates + measurement contract + GO / HOLD decision
/ 02
BUILD & RESCUE
Once the decision is clear, we work on the product.
For a new product, we implement the agreed scope. For a live product, we stabilize the system first and then move forward deliberately.
EXEC-01BUILD
Product implementation
I turn a FORGE build contract or an already-clear scope into a working digital product. Pricing depends on platforms, data model, integrations and delivery targets.
PRICING
Scope-based
EXEC-02RESCUE
Production Rescue & Stabilization
I identify critical production bugs, performance issues and technical risks, then restore the product to a reliable state.
Starting at
Türkiye / from 17,500 TL
Duration / 5-day sprint
FOCUSED SPECIALIST WORK
Work that does not need the full product pipeline
Quick Technical Review
A low-risk entry point for founders not ready for a full audit: a high-level scan of product, code, infrastructure and release.
Türkiye / 3,900 TL
Product Clarity Audit
I turn fragmented product decisions, user flows and technical priorities into an actionable roadmap.
Türkiye / from 8,500 TL
Information Architecture & Taxonomy
I turn fragmented content, category and information structures into discoverable, manageable and scalable systems.
Türkiye / from 25,000 TL / project
/ 03 · OPERATIONS
If the product is live, technical ownership has to stay live too.
To keep the product from drifting after a one-off project, release, maintenance, monitoring and regular technical intervention can run under one operating model.
NEW PROJECTS
Capacity open
OPERATE
Managed App Operations
Starting at
Türkiye / from 9,500 TL / month
OPS-01
Release & Maintenance
Türkiye / 9,500 TL / month
Up to 5 technical hours per month
OPS-02
Multi-Platform Operations
Türkiye / 17,500 TL / month
Up to 10 technical hours per month
OPS-03
Managed Product Operations
Türkiye / 29,500 TL / month
Up to 18 technical hours per month
- Web plus one application platform
- One scheduled release per month
- Deployment and store submission
- Basic bug fixes
WORK PROTOCOL
Four rules that reduce surprises.
No need for a wall of promises. These are the basic working rules that keep the project healthy.
PRT-01
Scope is locked first
Unapproved work is never silently added to implementation.
PRT-02
Repo and environments are the source
Ownership and working environments are defined before work starts.
PRT-03
A merge is not release evidence
Build, deploy and live verification are treated as separate gates.
PRT-04
Handoff avoids dependency
Code, architecture, deployment and critical operating notes are handed over.
Türkiye projects are quoted in TL; international projects can be quoted in USD or EUR. Currency and scope are locked in the proposal.
COMMERCIAL / CLEAR
Budget, timing and working model are clear before we start.
The goal is not to turn the proposal call into negotiation. It is to make the purchase, delivery window and start conditions visible up front.
The first fit call is free.
The initial call clarifies the problem, current state and sensible starting point. It is not a paid analysis or delivery session.
Price and scope are locked before work starts.
The figures below are typical scope bands. Exact fee, inclusions, exclusions and delivery target are fixed after written approval.
The delivery clock starts when required inputs are ready.
Typical delivery bands assume repository, access, data and decision inputs are available. Delayed dependencies can move the schedule.
No account-manager handoff.
The person diagnosing the problem also defines the scope, builds the system and delivers it, so decision context does not get lost between sales and execution.
SYSTEMTYPICAL SCOPETYPICAL DELIVERYDETAIL
BUILD / EXEC-01
Priced by scope. For a clearly defined product scope, a typical first implementation sprint is 10–20 business days; larger deliveries are phased in the proposal.
TERMS / BEFORE START
Cancellation, rescheduling, payment and any applicable warranty terms are written into the proposal for the specific service and approved before work starts; the site does not promise undefined outcome guarantees.
Delivery bands are business days for a typical scope with required inputs available. Larger scope, additional research or third-party dependencies are stated separately in the proposal.
SERVICES / DIRECT ANSWERS
Match the problem to the right intervention.
The services are not one generic consulting package. Uncertainty, production risk and continuous operations require different interventions.
A-01
What does digital product consulting include here?
It clarifies product decisions, scope, user flows, information and systems architecture, technical risk and the release path. Where needed, the work continues through implementation and live operations.
A-02
Can you take over a fragmented or unfinished live product?
Yes. I first review code, infrastructure, data, release history and critical risks. If there is a viable path, I stabilize the system, repair the release flow and make operations maintainable.
A-03
What is the difference between rescue and managed operations?
Rescue stabilizes a defined technical problem or risk set in a focused scope. Managed operations continuously owns releases, maintenance, monitoring, stores and technical operations through monthly capacity.
808 OS / PACKAGE + CART
Choose a package. Build the scope. See the estimate instantly.
808 OS is not packaged SaaS. The package defines the operating baseline; extra integrations, modules, automation and intelligence are priced separately in the cart. The fixed proposal is locked after Blueprint.
Review the 808 reference 808 BLUEPRINT
4,900 TL3–5 business days
Maps workflows, decision points, data sources, integration difficulty, screens/modules, permissions and delivery plan. If the build proceeds, the full 4,900 TL is credited to the project.
808 Core
Entry package for a focused operation
A focused control center that brings a small number of fragmented sources into one decision surface.
29,500 TL
10–15 business days
Package allowance
- Up to 2 standard data sources
- 1 primary control center + core operating views
- 1 automation flow
- Basic user access
Everything included
- 808 Blueprint and workflow map
- Responsive interface adapted to your brand
- Custom subdomain setup
- Production deploy and live verification
- Source-code and operating-note handoff
- 7 days of stabilization support
Best for: One team, one primary operating flow or a first 808 implementation.
808 Pro
Balanced operating package
The full 808 experience for multiple operating layers, automations and role-aware access in one center.
49,500 TL
15–20 business days
Package allowance
- Up to 5 standard data sources
- Up to 3 operating modules
- Up to 3 automation flows
- Advanced role / permission model
Everything included
- Everything in Core
- Decision queue, alerts and state signals
- Basic intelligence / rule layer
- Role-based visibility
- Advanced measurement and operating views
- 14 days of stabilization support
Best for: Founders, small teams, agencies or operations running multiple products/channels.
808 Custom
Complex and custom operations
Starting scope for operations requiring custom connectors, deeper workflows and advanced intelligence.
79,500 TL+
20–40 business days
Package allowance
- Up to 6 standard data sources
- 1 custom API / connector
- Up to 5 automation flows
- Advanced roles, permissions and intelligence layer
Everything included
- Everything in Pro
- Custom data contracts and connector development
- Advanced AI / intelligence decision layer
- Complex automation orchestration
- Custom module and workflow design
- 30 days of stabilization support
Best for: Multi-product, multi-team systems with custom APIs or deeper automation requirements.
EXTRA SCOPE
Add only what you need.
Extra standard integration
Connects one additional data source through a documented API or supported integration path.
+4,000 TL/ source
0
Extra custom API / connector
Builds an additional connector beyond package allowance for a system without a ready integration path or with a custom data contract.
+9,500 TL/ connector
0
Extra operating module
Adds another decision surface such as projects, revenue, content or support.
+4,500 TL/ module
0
Extra automation pack
Designs, implements and verifies two additional trigger/action flows.
+3,500 TL/ 2 flows
0
Advanced AI / intelligence
Adds summarization, classification, decision support or signal-to-action agent behavior.
+7,500 TL/ scope
Advanced roles & permissions
Adds role-based module/data visibility and controlled administrative permissions.
In package
Historical data migration
Cleans and imports existing CSV/Sheet/DB history into the agreed data contract.
+5,500 TL/ dataset
Real-time synchronization
Uses event/webhook-based data flow instead of polling where the source supports it.
+6,500 TL/ scope
Extra training & handoff session
A 60-minute live usage, administration and operating session for your team.
+3,500 TL/ session
0
Extra 30 days stabilization
Adds a post-handoff window for in-scope defects, integration breakage and small operating adjustments.
+6,500 TL/ 30 days
RULE-01
Blueprint and scope lock
The 808 Blueprint is 4,900 TL. If the build proceeds, the full amount is credited against the project total; otherwise it closes as a standalone deliverable.
RULE-02
Payment and milestones
Payment flow: 4,900 TL Blueprint → build kickoff topped up to 50% of total → 30% working-system approval → 20% production handover.
RULE-03
Third-party costs
Cloudflare, Supabase, OpenAI, Make/Zapier, email, SMS, paid API and similar third-party license/usage fees are excluded and, where possible, remain in the client's own account.
OUT OF SCOPE
What the price does not buy is explicit too.
- Building an unrelated standalone SaaS / mobile app from scratch
- Unauthorized private-API reverse engineering or access-control bypass
- Large-scale data cleansing, manual data entry or content operations outside selected scope
- New modules, integrations or product flows added after scope lock
- Ongoing maintenance/operations after handoff; scoped separately as a managed service
READY STARTS
Choose the problem. See the scope.
PKG-01
Product Audit
PROBLEM
The growth or sales bottleneck is unclear.
OUTCOME
Turns risks into one intervention order.
RELATED / GRAPH
FAQ-00FAQ.SECUI-L
FAQ
Everything you'd ask on a call, minus the call
Five questions, straight answers.
- how-it-works.frame
We start with a handover audit: code, infrastructure, release history and risks. Then access and roles are set up, a release calendar is agreed, and the monthly rhythm begins: planned releases, checks and a technical health report at month end.
- need-for-speed.frame
The first technical health report lands within about two weeks. The first planned release usually ships inside month one. Response time on live issues is one to three business days depending on the package.
- the-firehose.frame
Packages are not unlimited development — they hold 5, 10 or 18 technical hours per month. When capacity fills we prioritise together: non-urgent work rolls into next month, larger out-of-scope work is quoted separately.
- the-whole-thing.frame
Either. Release & Maintenance keeps web plus one app platform alive; Full Product Operations covers release planning, store management, backend monitoring and a monthly architecture review.
- the-do-over.frame
Yes — that is the work. I take over messy, half-finished or abandoned products and stabilise them. After the audit the risks are written down plainly; if something is technically unsustainable I say so before selling a package.