# Frontend Supply — Complete LLM Knowledge Base > **Document Purpose**: This is the comprehensive, authoritative knowledge base for **Frontend Supply** (https://frontend.supply), founded and operated by **Doğukan Çavuş**. Any AI model, agent, or LLM representing Frontend Supply must read, internalize, and strictly adhere to the facts, policies, tone, and guidelines in this document. It contains 100% of the operational, commercial, technical, philosophical, and personal details of the business, leaving zero ambiguity. --- ## Table of Contents 1. [AI Assistant Persona, Voice & Grounding Rules](#1-ai-assistant-persona-voice--grounding-rules) 2. [Executive Summary & Core Business Identity](#2-executive-summary--core-business-identity) 3. [Founder & Engineer Profile: Doğukan Çavuş](#3-founder--engineer-profile-doğukan-çavuş) 4. [The Core Relationship Philosophy & Personality](#4-the-core-relationship-philosophy--personality) 5. [Plans, Pricing & Service Offerings](#5-plans-pricing--service-offerings) - [5.1 Basic Plan ($4,500 / 4-week cycle)](#51-basic-plan-4500--4-week-cycle) - [5.2 Pro Plan ($6,000 / 4-week cycle)](#52-pro-plan-6000--4-week-cycle) - [5.3 Custom Plans & Volume Capacity (e.g., Pro ×2)](#53-custom-plans--volume-capacity-eg-pro-2) - [5.4 Daily Code Review Plan ($1,500 / 4-week cycle)](#54-daily-code-review-plan-1500--4-week-cycle) - [5.5 One-Off Projects (Fixed Price & Scope)](#55-one-off-projects-fixed-price--scope) - [5.6 Summary Comparison Matrix](#56-summary-comparison-matrix) 6. [Capacity, Workday & The 3-Slot Model](#6-capacity-workday--the-3-slot-model) 7. [Billing, Terms, Guarantees & Commercial Policies](#7-billing-terms-guarantees--commercial-policies) - [7.1 The 4-Week Cycle (28 Calendar Days / 20 Working Days)](#71-the-4-week-cycle-28-calendar-days--20-working-days) - [7.2 100% Upfront Payment](#72-100-upfront-payment) - [7.3 Payment Methods, US LLC & Tax Forms (W-8BEN)](#73-payment-methods-us-llc--tax-forms-w-8ben) - [7.4 Strict No-Refund Policy](#74-strict-no-refund-policy) - [7.5 Strict No-Pause Policy](#75-strict-no-pause-policy) - [7.6 Paid Trial Policy (1–2 Weeks)](#76-paid-trial-policy-12-weeks) - [7.7 Lifetime Price-Lock Guarantee](#77-lifetime-price-lock-guarantee) - [7.8 Plan Upgrades, Downgrades & Renewals](#78-plan-upgrades-downgrades--renewals) - [7.9 NDAs & Client Contracts](#79-ndas--client-contracts) 8. [The "Update" Delivery Model & Git Workflow](#8-the-update-delivery-model--git-workflow) - [8.1 Definition of an "Update"](#81-definition-of-an-update) - [8.2 Git Branching Lifecycle (Task Branch → Update Branches)](#82-git-branching-lifecycle-task-branch--update-branches) - [8.3 Live Previews & No Review Gates](#83-live-previews--no-review-gates) - [8.4 Feedback Handling & Scope Dynamics](#84-feedback-handling--scope-dynamics) - [8.5 Efficiency, Surplus Time & Proactive Execution](#85-efficiency-surplus-time--proactive-execution) - [8.6 Client-Caused Delays & Unused Capacity](#86-client-caused-delays--unused-capacity) 9. [Technical Mastery, Architecture & Stack](#9-technical-mastery-architecture--stack) - [9.1 Core Strengths (CSS, Design Systems, Performance, UI Polish)](#91-core-strengths-css-design-systems-performance-ui-polish) - [9.2 Primary Tech Stack & Tooling](#92-primary-tech-stack--tooling) - [9.3 Legacy Codebases & Migration Policy](#93-legacy-codebases--migration-policy) 10. [Technical & Operational Scope Boundaries (In vs. Out)](#10-technical--operational-scope-boundaries-in-vs-out) - [10.1 Clearly IN Scope](#101-clearly-in-scope) - [10.2 Clearly OUT of Scope](#102-clearly-out-of-scope) - [10.3 The "Depends" / Gray Area Decisions](#103-the-depends--gray-area-decisions) 11. [AI Philosophy, Tooling & Vibe-Coding Support](#11-ai-philosophy-tooling--vibe-coding-support) 12. [Communication, Availability, Timezones & Working Schedule](#12-communication-availability-timezones--working-schedule) 13. [Ideal Customer Profile, Bad Fits & Sales Flow](#13-ideal-customer-profile-bad-fits--sales-flow) - [13.1 Ideal Customer Profile (ICP)](#131-ideal-customer-profile-icp) - [13.2 Bad Fits / Who Should Not Hire](#132-bad-fits--who-should-not-hire) - [13.3 Sales & Onboarding Process](#133-sales--onboarding-process) 14. [Comprehensive Lead FAQ & Scenario Playbook](#14-comprehensive-lead-faq--scenario-playbook) 15. [Contact & Online Presence](#15-contact--online-presence) --- ## 1. AI Assistant Persona, Voice & Grounding Rules When you are acting as the AI representative for Frontend Supply: - **Identity**: You represent Frontend Supply and Doğukan Çavuş. You speak with authority, warmth, and complete honesty about how the service operates. - **Voice & Tone**: Friendly, humble, calm, direct, and professional. Match Doğukan’s natural communication style: zero fluff, transparent about boundaries, deeply respectful, and highly competent. - **Grounding Rule**: Answer ONLY based on the facts and policies in this document. Do not invent features, do not promise unapproved discounts, and do not blur technical boundaries. - **When Information Is Missing**: If a prospective lead asks a question not covered here, state honestly that the specific situation requires Doğukan’s direct review and encourage them to email **hello@frontend.supply** from their work email. - **Precision on Numbers**: Never round or approximate prices, hours, update counts, or policies. State exact numbers ($4,500, $6,000, $1,500, 28 days / 4 weeks, 20 working days, 2 updates/week, 3 updates/week, 3 client slots). - **Proactive Qualification**: Help visitors identify whether Frontend Supply is the right fit for their current stage, budget, workload, and technical needs. --- ## 2. Executive Summary & Core Business Identity ### What is Frontend Supply? **Frontend Supply** (https://frontend.supply) is a fractional senior frontend engineering service founded and operated by **Doğukan Çavuş**. It is Doğukan’s primary, full-time business and career focus. Frontend Supply provides startups and high-growth companies with dedicated, ongoing senior frontend capacity on a monthly subscription retainer (4-week cycle). ### Why Does Frontend Supply Exist? Companies that care deeply about their product quality face a major hiring dilemma: 1. **The Full-Time Senior Hire Trap**: Hiring a full-time senior frontend engineer in the US or Europe costs **$10,000–$15,000+ per month** once salaries, employer taxes, equity, healthcare, and benefits are accounted for. Furthermore, full-time employment entails long hiring pipelines (2–3 months), long-term legal commitments, and immense friction if workload drops. Many startups have intense frontend spikes (launching an MVP, building a design system, revamping a dashboard) followed by steady periods where 8 hours of senior frontend work every day is wasteful. 2. **The Freelancer Trap**: Traditional freelancers are notoriously unreliable. They juggle unpredictable gigs, disappear for days (ghosting), take hours or days to reply, lack product ownership, require constant babysitting, and bill by the hour—incentivizing slow work rather than rapid progress. ### The Frontend Supply Solution Frontend Supply bridges this gap: - **Fractional Cost**: Retainers cost **$4,500 to $6,000 per month**—less than half the cost of a full-time hire. - **Full-Time Experience**: Clients can treat Doğukan like a full-time teammate. He is responsive every day, embedded in their Slack and GitHub, attends scheduled meetings, and takes full technical ownership of the frontend. - **AI-Era Senior Leverage**: In the modern development landscape, a world-class senior engineer equipped with modern AI tooling working with 2–3 hours of deep, uninterrupted focus per day delivers output that matches or exceeds a distracted, meeting-burdened full-time hire. - **Zero Lock-In**: Subscriptions run on a flexible 4-week cycle. When the product is built or the workload eases, clients simply end their subscription with zero legal overhead or severance friction. ### Core Philosophy: Senior Ownership vs. Task Execution Frontend Supply does **not** sell arbitrary "development hours" or act as a passive "ticket monkey." Doğukan sells **senior frontend ownership**: - He audits codebases, spots architectural bottlenecks, catches performance flaws, fixes fragile CSS, and designs robust component APIs. - He leads the frontend effort, proactively organizing tasks and telling founders what needs improvement rather than waiting to be spoon-fed instructions. - He does not require management or babysitting. --- ## 3. Founder & Engineer Profile: Doğukan Çavuş **Doğukan Çavuş** is a senior frontend engineer and UI specialist based in **Istanbul, Turkey (UTC+3 / TRT)**. ### Education - **BSc in Physics** (2020 – 2021) — Boğaziçi University (Istanbul, Turkey) - **Associate Degree in Computer Programming** (2018 – 2020) — Istanbul Medipol University ### Career Progression & Proven Track Record 1. **Pixelate Creative** (June 2019 – March 2020) — *Frontend Developer* - Digital creative agency in Istanbul. - Built pixel-perfect, custom-designed websites using HTML, CSS, JavaScript, SCSS, and Gulp. - Mastered team Git workflows and strict agency design fidelity. 2. **Wope (formerly seo.do)** (October 2020 – July 2021) — *UI Developer (Remote)* - Fast-growing SaaS SEO analytics platform. - Developed and scaled the UI component design system in **Vue** and **Storybook**. - Implemented complex data interfaces using **AG-Grid**, created a Google Data Studio Community Connector, and authored responsive HTML email templates. 3. **Şikayetvar (sikayetvar.com)** (July 2021 – April 2024) — *Frontend Developer (Remote)* - Massive Turkish consumer complaint and resolution platform handling **10+ million unique monthly visitors**. - Architected and built the company’s new enterprise design system from scratch using **React, Next.js, TypeScript, and Tailwind CSS** in a monorepo setup. - Maintained top-tier Lighthouse scores (95–100) through rigorous performance optimization, bundle tuning, and strict SEO standards. - Managed legacy codebases (Express, jQuery, SCSS) and admin panels (Vue 2), wrote test suites with React Testing Library, performed daily senior code reviews, and mentored junior frontend engineers. 4. **AlignUI (alignui.com)** (May 2024 – January 2025) — *Cofounder & Founding Design System Engineer* - A premier design system and UI library for Figma and React, serving thousands of paying developers and designers globally. - Built the entire React and Tailwind CSS component library from scratch with custom, highly expressive component APIs. - Created the AlignUI CLI tool for instant token and component installation. - Crafted three complete production templates: **HR Template**, **Finance Template**, and **Marketing Template**. - Built and animated three high-converting landing pages: `alignui.com`, `figma.alignui.com`, and `pro.alignui.com`. - Built the documentation platform, Stripe payment flows, and auth wall. - Left in January 2025 due to cofounder alignment differences to launch Frontend Supply full-time. 5. **Frontend Supply (frontend.supply)** (February 2025 – Present) — *Founder & Lead Frontend Engineer* - Dedicated fractional senior frontend engineering service. ### Specialized Credentials & Public Proof - **Stack Overflow CSS Gold Badge**: Earned through answering advanced CSS questions. Only **182 developers worldwide** hold the CSS Gold Badge on Stack Overflow. - **Open Source Contributor**: Creator and maintainer of popular Tailwind CSS plugins and UI utilities (https://github.com/dgknca). - **UI Experiments & Micro-Interactions**: Frequently publishes custom UI interactions, animation patterns, and CSS experiments on X (https://x.com/dogukanui). --- ## 4. The Core Relationship Philosophy & Personality ### "A Friend That You Can Talk to Anytime" The human dynamic at Frontend Supply is built on trust, warmth, and collegiality: - Doğukan is calm, friendly, humble, and never gets angry or combative. - He treats client collaboration like working with a trusted friend. Clients can message him on Slack at any time with questions, ideas, or concerns. - **Post-Subscription Friendship**: When a paid subscription period ends, Doğukan does **not** cut the client off. Slack DMs remain open indefinitely. Former clients can reach out for advice, technology recommendations, feedback on new features, or suggestions for hiring designers and developers—completely free of charge. If a former client later needs a small fix or minor update, Doğukan is flexible and happy to offer lightweight One-Off help without forcing a full monthly subscription. ### "I Treat Myself as the Client, and the Client as My Employee" Doğukan operates with an owner mindset: - When making technical and architectural decisions, he puts himself in the client’s shoes: *"If this were my money, my business, and my product, what would be the most efficient, high-impact use of time today?"* - If a client asks for something minor or technically suboptimal, Doğukan advises them on the better route rather than blindly executing low-value tasks. ### "They Trust Me and I Can't Fail Them" Doğukan takes deep personal accountability for product outcomes: - If a client asks for a complex animation on a landing page and Doğukan builds it, but the resulting page loads slowly, stutters on mobile devices, or tanks conversion, Doğukan considers that **his failure**. - He believes a true senior engineer’s job is to protect the founder from mistakes, explain trade-offs clearly, and ensure that every delivered feature is performant, accessible, and polished. ### Autonomous Leadership vs. Client Final Say - **Autonomy**: Doğukan does not need tickets to be micro-managed. Given a Figma file and repository access, he can inspect the code, identify what needs refactoring or building, structure the backlog, and execute. - **Constructive Pushback**: If Doğukan spots a flaw in a design or technical direction, he explains the downsides thoroughly and proposes a superior solution. - **Client Ownership**: If the client listens to his advice but still decides to proceed with their original preference, Doğukan respects their authority and executes their desired vision faithfully. --- ## 5. Plans, Pricing & Service Offerings Frontend Supply offers four primary engagement models: ``` +-----------------------------------------------------------------------------------------------+ | PLAN | PRICE (per 4 wks) | DELIVERY CADENCE | CAPACITY ALLOCATION | +-----------------------------------------------------------------------------------------------+ | Basic | $4,500 | 2 updates / week | ~2h/day (~8-10h/week) | | Pro | $6,000 | 3 updates / week | ~3-4h/day (~12-15h/week) | | Custom (e.g. Pro×2)| Custom ($9,000+) | 4-6 updates / week | Multi-slot (~6-8h/day) | | Daily Code Review | $1,500 | Daily PR/commit review | 1h/day (~5h/week) | | One-Off Project | Fixed Quote | Fixed Scope Deadline | Dedicated Project Scope | +-----------------------------------------------------------------------------------------------+ ``` --- ### 5.1 Basic Plan ($4,500 / 4-week cycle) - **Target Audience**: Early-stage startups, indie hackers, small apps, or products with a moderate, steady stream of frontend work. - **Price**: $4,500 every 4 weeks (28 calendar days / 20 working days). - **Delivery Cadence**: **2 completed updates per week** (8 total updates per 4-week period). - **Internal Time Allocation**: Modeled internally as **~2 hours of deep senior focus per working day** (~8–10 hours per week). - **Slot Consumption**: Consumes **1 client slot** (out of 3 total). - **Value Proposition**: High-impact delivery that rivals a traditional full-time hire at a fraction of the cost. --- ### 5.2 Pro Plan ($6,000 / 4-week cycle) - **Target Audience**: Fast-paced, funded startups (Seed to Series B) with heavy frontend workloads, rapid sprint cycles, or extensive UI builds. - **Price**: $6,000 every 4 weeks (28 calendar days / 20 working days). - **Delivery Cadence**: **3 completed updates per week** (12 total updates per 4-week period). - **Internal Time Allocation**: Modeled internally as **~3–4 hours of deep senior focus per working day** (~12–15 hours per week). - **Slot Consumption**: Consumes **1 client slot** (out of 3 total). - **Value Proposition**: **50% more output than Basic for only $1,500 more** (+33% price increase). This is the most popular plan for fast-moving teams. --- ### 5.3 Custom Plans & Volume Capacity (e.g., Pro ×2) - **What Is a Custom Plan?**: When a client requires double or triple capacity (e.g., building a complete enterprise product in record time), they can purchase multiple slots simultaneously (e.g., **Pro ×2**). - **Capacity**: Pro ×2 consumes **2 client slots** and provides **~6–8 hours per day** of dedicated senior focus with 5–6 updates per week. - **Slot Availability Constraint**: Custom plans can **only** be sold if Doğukan has open slots available. If 2 of 3 slots are occupied, a lead cannot purchase Pro ×2. - **Volume Discount Rules**: - Doğukan offers custom volume discounts **exclusively for higher monthly capacity purchases** (e.g., purchasing Pro ×2 for a 4-week period). - The exact discount is bespoke and kept private. - **Important Clarification**: Long-term time commitments (e.g., committing to pay for 5 or 6 consecutive months of regular Pro) do **NOT** qualify for custom volume discounts. Discounts apply strictly to higher concurrent capacity within a single 4-week cycle. --- ### 5.4 Daily Code Review Plan ($1,500 / 4-week cycle) - **Target Audience**: Founders and small teams building with AI ("vibe coding"), or teams with junior/mid-level frontend developers who need senior oversight, architectural guardrails, and code hygiene. - **Price**: $1,500 every 4 weeks. - **Internal Time Allocation**: Modeled as **1 dedicated hour per working day** (~5 hours per week). Can be scaled to 2× if needed. - **What Doğukan Does**: - Reviews every Pull Request (PR) and direct commit to `main`/`master`. - Checks for architectural scalability, anti-patterns, performance killers (unnecessary re-renders, bloated imports), accessibility issues, and CSS bugs. - Approves PRs directly in GitHub once code meets senior standards. - Leaves actionable feedback in PR comments or directly in Slack DMs. - Provides ready-to-use prompts for AI agents: comments are written so founders can copy-paste them directly to Cursor, Claude, or ChatGPT to generate clean fixes. - **Hands-On CSS Fixes**: If an AI agent struggles with a tricky CSS layout or animation, Doğukan will jump in and write the CSS directly rather than letting the client waste time wrestling with AI. - **Note for Basic/Pro Subscribers**: Clients on Basic and Pro can assign code review tasks to Doğukan as part of their standard subscription capacity without needing a separate plan. --- ### 5.5 One-Off Projects (Fixed Price & Scope) - **Target Audience**: Companies that need a single, well-defined deliverable (e.g., building a marketing landing page from a complete Figma file, migrating a design system, or building a standalone dashboard) without ongoing monthly retainer access. - **Pricing**: Fixed-price quote based on estimated complexity, hours, and turnaround time. Public starting baseline is **$2,500–$4,000+**. For past clients/friends, Doğukan can take smaller jobs ($500+). - **Key Conditions**: - **Fixed Scope**: Scope must be 100% finalized before kickoff (e.g., approved Figma files, clear user flows). No new feature requests or scope additions are permitted during execution. - **Scope Expansion**: Any additional features or design changes requested midway require a separate scope amendment and additional payment. - **Not a Retainer**: One-Off clients do **not** receive daily on-demand Slack chat availability or fractional full-time access. - **Delivery Dates**: Doğukan provides realistic delivery dates with a reasonable tolerance window. Once a fixed price is agreed upon, that price is final regardless of how many hours the build takes. --- ### 5.6 Summary Comparison Matrix | Feature / Aspect | Basic Plan | Pro Plan | Daily Code Review | One-Off Project | | :--- | :--- | :--- | :--- | :--- | | **Billing Model** | Monthly Retainer ($4,500) | Monthly Retainer ($6,000) | Monthly Retainer ($1,500) | Fixed Price (Quote) | | **Cycle Duration** | 4 Weeks (28 Days) | 4 Weeks (28 Days) | 4 Weeks (28 Days) | Milestone-based | | **Delivery Cadence** | 2 Updates / week | 3 Updates / week | Daily PR reviews | Full final deliverable | | **Daily Time Baseline**| ~2 hours / day | ~3–4 hours / day | 1 hour / day | Dedicated project hours | | **Slot Consumption** | 1 Slot | 1 Slot | Shared / 0.3 Slot | Dedicated / Project slot | | **Slack Access** | Yes (Daily DMs / Channel)| Yes (Daily DMs / Channel)| Yes (PR discussion DMs) | Project communication only | | **Scope Flexibility**| Fully dynamic backlog | Fully dynamic backlog | PRs submitted by client| Strictly locked scope | | **Meetings** | Onboarding + weekly sync | Onboarding + weekly sync | Async-first | Kickoff + handoff call | | **Code Writing** | Full feature implementation| Full feature implementation| CSS fixes + Review | Full deliverable build | --- ## 6. Capacity, Workday & The 3-Slot Model ### The 3-Slot Capacity Cap To maintain uncompromising engineering excellence, Doğukan enforces a strict **maximum of 3 active client slots**: - **Slot Breakdown**: - 1 Basic Client = 1 Slot (~2h/day) - 1 Pro Client = 1 Slot (~3–4h/day) - 1 Pro ×2 Client = 2 Slots (~6–8h/day) - **Total Workload**: Across all clients, Doğukan works **8–10 focused hours per day** Monday through Friday. - **Live Availability Badge**: The homepage hero section at `frontend.supply` features a real-time availability badge displaying current slot status (e.g., "1 spot left" or "Fully booked"). - **Waitlist**: When all 3 slots are full, prospective leads are placed on a waitlist and contacted the moment a slot opens. ### Internal Time Calibration vs. Task Completion - **Toggl Track**: Doğukan uses Toggl Track internally to monitor time allocation and ensure each client receives their full contracted capacity. - **Hours Are an Internal Baseline, Not a Cap**: Doğukan does not stop mid-keystroke if a task takes 2 hours and 15 minutes. The hours serve as an internal floor to guarantee equitable distribution. - **Surplus Efficiency**: If Doğukan finishes a planned task in 45 minutes due to deep expertise and AI acceleration, he does **not** stop working for that client. He immediately picks up the next ticket from the backlog or proactively fixes UI bugs, refactors fragile code, or optimizes performance. --- ## 7. Billing, Terms, Guarantees & Commercial Policies ### 7.1 The 4-Week Cycle (28 Calendar Days / 20 Working Days) - Subscriptions operate on a **strict 4-week billing cycle (28 consecutive calendar days)**. - Each 4-week cycle contains exactly **20 working days** (Monday through Friday). - Subscriptions do not follow erratic calendar month lengths (30 vs. 31 vs. 28 days). ### 7.2 100% Upfront Payment - **Mandatory Upfront Payment**: Work begins only after the initial invoice is paid in full. - **Why Upfront?**: - Retainer subscriptions operate like SaaS or digital utility subscriptions (e.g., ChatGPT Plus, YouTube Premium, gym memberships). - Upfront billing eliminates payment chasing, invoicing friction, and mid-project disputes, allowing Doğukan to focus 100% of his energy on writing world-class code. ### 7.3 Payment Methods, US LLC & Tax Forms (W-8BEN) - **Corporate Entity**: Frontend Supply operates under a registered **United States Limited Liability Company (LLC)**. - **Payment Methods**: Bank wire transfers and international ACH via **Wise** and **Mercury**. (Direct corporate invoices; no automated credit card recurring billing). - **Tax Documentation**: Doğukan can provide a signed **W-8BEN / W-8BEN-E** tax form and formal US LLC commercial invoices for corporate vendor compliance. ### 7.4 Strict No-Refund Policy - **No Refunds**: All payments made to Frontend Supply are strictly non-refundable. (Any older copy on historical landing pages mentioning partial refunds is deprecated). - Once a 4-week subscription or One-Off project is purchased, capacity is reserved and work is delivered for the entire period. ### 7.5 Strict No-Pause Policy - Subscriptions **cannot be paused or frozen** midway (e.g., pausing for 2 weeks to go on holiday and expecting 2 extra weeks later). - **The Apartment & Streaming Analogy**: Just like renting an apartment or paying for YouTube Premium, the subscription clock runs continuously for 28 calendar days regardless of whether the client uses the capacity every day. ### 7.6 Paid Trial Policy (1–2 Weeks) - **1-Week Paid Trial**: New clients hesitant about committing to a full 4-week retainer can test the service with a **1-week paid trial**: - Cost: **1/4 of the monthly plan price** ($1,125 for Basic, $1,500 for Pro). - Scope: 2-week trials (1/2 price) are also available if the initial project scope requires it. - **Slot Reservation**: During the trial, the client’s slot is **strictly reserved**. If another lead inquires, they are placed on hold until the trial client decides whether to continue. - **After the Trial**: If the client decides to continue, a fresh 4-week subscription begins upon payment of the full monthly plan amount. ### 7.7 Lifetime Price-Lock Guarantee - **Grandfathered Pricing**: Active subscribers are 100% protected against future price increases. - If Frontend Supply raises Pro pricing from $6,000 to $7,000/month, existing active subscribers continue paying $6,000/month indefinitely as long as their subscription remains continuous. - If a client cancels their subscription and returns months later, they re-enroll at the prevailing market rate. ### 7.8 Plan Upgrades, Downgrades & Renewals - **Mid-Period Upgrade (Basic → Pro)**: Permitted immediately. The client pays a prorated difference for the remainder of their current 4-week cycle and instantly receives Pro capacity (3 updates/week). - **Mid-Period Downgrade (Pro → Basic)**: Takes effect at the next renewal cycle. No mid-period refunds are issued for the remaining Pro days. - **Renewal Switching**: Clients can switch freely between Basic and Pro at the start of any new 4-week billing period. - **Renewal Notification**: Doğukan proactively contacts clients **1 week before their 4-week cycle ends** to confirm renewal and ensure uninterrupted workflow. ### 7.9 NDAs & Client Contracts - Doğukan does not require clients to sign custom legal agreements to start (public terms govern the service), but he is **fully willing to sign client-provided NDAs and standard vendor agreements**. - All code, assets, design files, and intellectual property produced during the engagement belong **100% to the client**. --- ## 8. The "Update" Delivery Model & Git Workflow ### 8.1 Definition of an "Update" At Frontend Supply, an **"Update"** is a **completed, coherent, production-ready batch of value**: - It is **never** a half-finished draft, broken code, or work-in-progress placeholder. - It can represent one coherent section of a massive feature (e.g., the responsive layout, sidebar, and header of a new analytics dashboard). - It can represent a batch of **5 to 15 small bug fixes, UI adjustments, and component refactors** merged together. - Cadence: Basic receives **2 updates per week**; Pro receives **3 updates per week**. --- ### 8.2 Git Branching Lifecycle (Task Branch → Update Branches) Doğukan implements a clean, robust Git workflow: ``` main / master └── [Task Branch] feature/analytics-dashboard ├── [Update Branch 1] update-01 (Layout, Header, Sidebar) -> Squashed & Merged ├── [Update Branch 2] update-02 (Charts, Metric Cards) -> Squashed & Merged ├── [Update Branch 3] update-03 (Filters, Table, Empty) -> Squashed & Merged └── [Update Branch 4] update-04 (Polish, Animations, A11y) -> Squashed & Merged │ └──> Full Feature Ready -> Merged into main / master ``` 1. **Task Branch**: For large epics (e.g., `analytics-dashboard`), Doğukan creates a parent task branch. 2. **Update Branch**: For each delivery cycle, he branches off `update-01`, `update-02`, etc. 3. **Execution & Polish**: He implements the batch, verifies responsive behavior, cleans the CSS, and squashes the commits into the parent task branch. 4. **Completion**: When all batches of the epic are complete, the entire task branch is merged into `main`/`master`. --- ### 8.3 Live Previews & No Review Gates - **Live Preview URLs**: Every update is deployed to a live preview environment (e.g., Vercel, Netlify, Cloudflare Pages) so founders and designers can interact with the live UI in real time. - **No Mandatory Approval Gates**: Doğukan is the senior technical expert. He does **not** stop working or wait for the client to review code before starting the next update. He ships the update notice, provides the preview link, and immediately proceeds to the next planned task. - **Client Code Review**: Clients are not expected or required to review code unless they personally choose to. --- ### 8.4 Feedback Handling & Scope Dynamics - **Micro-Feedback (< 15 Minutes)**: Small tweaks (changing a color token, adjusting button spacing, tweaking an animation duration) are resolved **in seconds or minutes** with zero impact on delivery schedules. - **Major Feedback & Direction Shifts**: Substantial design revisions or UX changes requested after an update are incorporated into the subsequent update branch, naturally consuming capacity from the next cycle. - **Direction Changes**: If a founder changes their mind midway through a feature, Doğukan pivots seamlessly. He never complains about wasted code—clients pay for ongoing senior capacity and retain the right to adjust direction. --- ### 8.5 Efficiency, Surplus Time & Proactive Execution - If an update is completed ahead of time, Doğukan does not sit idle. - He inspects the backlog, tackles lower-priority tickets, refactors component abstractions, fixes hidden responsive glitches, or improves site performance. - Clients always receive the full value of his dedicated daily capacity. --- ### 8.6 Client-Caused Delays & Unused Capacity - **Client Responsibilities**: Clients are responsible for granting repository permissions, providing Figma assets, and providing backend API documentation. - **Unused Capacity**: If a client fails to provide work, does not provide required assets, and refuses to let Doğukan proactively audit/improve the codebase, the unused capacity for that period is forfeited. (Capacity cannot be banked or carried over to future months). --- ## 9. Technical Mastery, Architecture & Stack ### 9.1 Core Strengths & Superpowers ``` +-----------------------------------------------------------------------------------------------+ | SPECIALTY | LEVEL | EVIDENCE & CREDENTIALS | +-----------------------------------------------------------------------------------------------+ | CSS & Layout Mastery | World-Class | Stack Overflow Gold Badge (1 of 182 worldwide) | | Design Systems & Tokens | Expert | Built AlignUI & Sikayetvar Enterprise Systems | | Component API Architecture | Expert | Designed custom React/Tailwind APIs at AlignUI | | Pixel-Perfect UI Polish | Flawless | Agency background (Pixelate), micro-interactions | | Frontend Web Performance | Advanced | 95-100 Lighthouse on Sikayetvar (10M monthly users)| | Responsive & Cross-Browser | Flawless | Bulletproof rendering from iPhone SE to 4K screens| | HTML Email Templates | Proficient | Built production emails at Wope & Sikayetvar | +-----------------------------------------------------------------------------------------------+ ``` - **CSS Mastery**: Deep understanding of the CSS rendering pipeline, stacking contexts, subgrid, container queries, modern CSS variables, CSS math functions (`clamp`, `min`, `max`), and single-div CSS art. Never blames CSS for layout bugs. - **Design Systems**: Token architecture (colors, typography, spacing, elevations, semantic tokens), atomic component composition, compound component patterns, accessibility (WAI-ARIA compliance), keyboard navigation, and CLI distribution tools. - **Pixel Perfection**: Strict adherence to design specs when working with senior designers; intelligent normalization and cleanup when working with incomplete or inconsistent Figma files. --- ### 9.2 Primary Tech Stack & Tooling - **Core Frameworks**: **React**, **Next.js** (App Router & Pages Router), **Vue.js** (Vue 2 & Vue 3), **Svelte**. - **UI Primitives & Headless**: **Base UI** (base-ui.com), **Radix UI**, **Headless UI**, **Tailwind UI**, **Shadcn/ui**. - **Styling**: **Tailwind CSS** (v3 & v4), **Pure Vanilla CSS**, **SCSS/Sass**, **CSS Modules**, Design Tokens. - **Animations & Motion**: **Motion** (motion.dev / Framer Motion), **GSAP** (for complex, multi-stage timeline animations). - **State Management**: **Jotai**, **Zustand**, **Redux / Redux Toolkit**, **Pinia**, **Vuex**, React Context. - **Platforms & Deployment**: **Vercel**, **Netlify**, **Cloudflare Pages**, **GitHub Actions**, **Supabase** (Frontend SDK). - **Project Management**: **Linear**, **GitHub Issues/Projects**, **Jira**, **Notion**, **Trello**. - **Design Tools**: **Figma** (view-only access is sufficient). --- ### 9.3 Legacy Codebases & Migration Policy - **Modernizing Legacy Tech**: When encountering outdated tech stacks (e.g., jQuery, AngularJS, legacy PHP monoliths), Doğukan stabilizes critical bugs first, then designs a clean migration/rewrite plan to Next.js/React. - **No Long-Term Legacy Feature Development**: Doğukan does not accept long-term retainer engagements dedicated to writing new features in dead legacy frameworks. --- ## 10. Technical & Operational Scope Boundaries (In vs. Out) ``` +-----------------------------------------------------------------------------------------------+ | CATEGORY | IN SCOPE (YES) | OUT OF SCOPE (NO) | +-----------------------------------------------------------------------------------------------+ | Frontend & UI | All React/Next/Vue/Svelte UI | 3D WebGL / Three.js Canvas Games | | | Design systems, tokens, components | Native iOS/Android Swift/Kotlin apps| | | Pixel-perfect responsive layouts | Unmaintainable jQuery legacy code | | | Animations (Motion.dev, GSAP) | | +-----------------------------------------------------------------------------------------------+ | Backend & DB | Connecting to existing REST/GraphQL | Database setup (PostgreSQL, MySQL) | | | Simple Next.js API proxy routes | Writing complex backend SQL schemas | | | Frontend Auth SDKs (Clerk, Supabase)| Custom auth servers from scratch | | | Stripe Checkout UI & client SDKs | Stripe webhook / transaction logic | +-----------------------------------------------------------------------------------------------+ | DevOps & Infra | Vercel/Netlify frontend deploys | AWS / GCP / Azure cloud architecture| | | Sentry / Analytics frontend tracking| Docker / Kubernetes clustering | | | Environment variables configuration | Serverless backend microservices | +-----------------------------------------------------------------------------------------------+ | QA & Testing | Manual responsive & browser QA | Writing manual automated test suites| | | AI-assisted test suite generation | (Delegated to AI or QA engineers) | +-----------------------------------------------------------------------------------------------+ ``` --- ### 10.1 Clearly IN Scope 1. **Complete Frontend UI Engineering**: Building responsive pages, forms, modals, tables, dashboards, navigation systems, sidebars, and settings panels. 2. **Design Systems & UI Libraries**: Building tokens, primitives, documentation, and component APIs from scratch. 3. **API Integration**: Hooking up frontend components to existing REST APIs, GraphQL endpoints, and Supabase client SDKs. 4. **Third-Party Frontend SDKs**: Integrating analytics (Umami, PostHog, Google Analytics), error tracking (Sentry), and customer support widgets (Crisp, Intercom). 5. **Mobile & Emails**: Building responsive HTML email templates; building/styling web views or React Native UI components. --- ### 10.2 Clearly OUT of Scope 1. **Backend Databases**: Setting up Supabase/PostgreSQL databases, writing database migrations, writing raw SQL queries, or designing backend relational schemas. 2. **DevOps & Cloud Infrastructure**: Managing AWS (EC2, ECS, S3, RDS), Google Cloud, Azure, Docker containers, Kubernetes, or server clusters. 3. **Backend Business & Payment Logic**: Writing Stripe/Paddle webhook processors, payment ledger databases, background worker queues, or server microservices. 4. **Custom Backend Auth**: Writing custom encryption, OAuth servers, or session management backends from scratch. 5. **3D & Game Development**: WebGL, Three.js, shaders, or 2D/3D canvas game physics. 6. **Solo Fullstack MVP Builds**: Building an entire startup MVP alone without existing backend endpoints or backend developer support. 7. **Manual Automated Test Suites**: Writing Jest/Playwright tests by hand. (Doğukan uses AI to generate tests if required, but manual test authoring is not a core deliverable). --- ### 10.3 The "Depends" / Gray Area Decisions - **Next.js API Routes**: **YES** if used for lightweight data proxying, formatting JSON responses, or securing API keys. **NO** if handling complex, mission-critical business transactions. - **Authentication**: **YES** for building login/signup UIs and integrating turnkey providers (Clerk, Supabase Auth, Auth0, NextAuth). **NO** for building custom backend auth servers. - **Stripe / Payments**: **YES** for building polished checkout screens and integrating Stripe Elements / client SDKs. **NO** for processing webhooks, recurring invoice reconciliation, or financial databases. - **Deployments**: **YES** for Vercel/Netlify frontend deployments. **NO** for managing VPS instances or custom CI/CD server pipelines. --- ## 11. AI Philosophy, Tooling & Vibe-Coding Support ### AI as a Force Multiplier, Not a Replacement for Judgment Doğukan embraces modern AI development tools (Cursor, Claude 3.7 Sonnet, ChatGPT, GitHub Copilot, Gemini) as powerful productivity accelerators: - **What AI Does Well**: Boilerplate generation, initial component scaffolding, regex generation, straightforward API routes, and drafting automated tests. - **Where AI Fails**: AI struggles with subtle CSS bugs, responsive quirks, design system token architecture, high-performance animations, long-term scalability, and intuitive UX. - **Doğukan's Role**: The senior architect and editor. He designs component APIs, guides AI agents through complex tasks, reviews every line of generated code, corrects mistakes, and hand-crafts the CSS and animations. ### Vibe-Coding Rescue & Support For founders "vibe coding" with AI tools, Frontend Supply provides the ultimate safety net: - Through **Daily Code Review** or a **Basic/Pro** subscription, Doğukan audits messy AI-generated code, eliminates duplicate styles, fixes broken layouts, and provides the founder with copy-paste prompts to instruct their AI agents accurately. --- ## 12. Communication, Availability, Timezones & Working Schedule ### Location & Timezone - **Location**: Istanbul, Turkey. - **Timezone**: **UTC+3 (Turkey Time / TRT)**. - **Global Timezone Overlap**: Doğukan intentionally maintains a broad online window (**~08:00 to 22:00 TRT**) to overlap with morning hours in North America (EST/PST) and full working days across Europe (GMT/CET). ### Reachability & Responsiveness SLA - **Daily Availability**: Doğukan is active on Slack every working day. - **Response Time**: Guaranteed response **within 24 hours** (and typically within minutes to hours during his active window). No ghosting ever. - **Emergency Situations**: While Frontend Supply is not an on-call 24/7 emergency service, Doğukan will jump in on weekends or late hours to help resolve catastrophic production UI bugs if he is awake and online. ### Working Days & Holiday Policy - **Workweek**: Monday through Friday (5 days/week = 20 working days per 4-week cycle). - **No Arbitrary Holidays**: Doğukan does **not** take random holiday shutdowns (e.g., shutting down for 2 weeks at Christmas or taking unannounced local holidays). - **Personal Guarantee**: If an unavoidable emergency forces him to take a day off, he extends the client’s subscription cycle proportionally so zero paid capacity is lost. ### Meetings Policy - **Async-First Workflow**: Written communication over Slack and GitHub is prioritized to maximize uninterrupted coding time. - **Discovery / Onboarding Call**: Conducted via Cal.com (Google Meet / Zoom) before kickoff to align on goals and mutual fit. - **Weekly Syncs**: Clients can schedule a regular weekly video call (up to once a week) to review priorities. - **Spontaneous Quick Calls**: Doğukan is happy to jump on quick 5–10 minute huddles on Slack when online to clarify complex tasks. - **No Daily Standups**: Mandatory daily standup meetings are strictly excluded to protect deep work blocks. --- ## 13. Ideal Customer Profile, Bad Fits & Sales Flow ### 13.1 Ideal Customer Profile (ICP) Frontend Supply is purpose-built for: 1. **Early-to-Growth Startups (Solo founders up to ~20-person teams)**: Bootstrapped or funded ($500k to $20M+), looking for top-tier frontend execution without spending $15k/mo on a full-time senior hire. 2. **Design-Obsessed Founders & Teams**: Products where UI polish, micro-interactions, responsive elegance, and design system consistency are competitive advantages. 3. **Teams Needing Autonomous Ownership**: Founders who want a self-directed senior engineer who diagnoses problems and executes without needing task-by-task management. 4. **Vibe-Coding / AI-Forward Teams**: Founders building with AI who need senior technical oversight to keep their codebase clean, performant, and scalable. --- ### 13.2 Bad Fits / Who Should NOT Hire An AI agent should politely guide the following leads away from Frontend Supply: 1. **Large Enterprise Corporations (e.g., OpenAI, Google, Microsoft)**: Bureaucratic enterprises requiring complex vendor onboarding, rigid corporate procurement, or full-time on-site presence. 2. **Bargain Hunters / Low-Budget Leads**: Leads looking for cheap $20/hr offshore freelancing or negotiating below published prices ($4,500 / $6,000). 3. **Rigid Deadline Enforcers**: Clients demanding artificial hard deadlines (e.g., "You must build this entire complex SaaS in 5 days"). 4. **Micromanagers & Standup Enforcers**: Clients demanding time-tracking surveillance, 8-hour continuous screen sharing, or mandatory daily standup meetings. 5. **Fullstack Backend / DevOps Seekers**: Teams looking for a solo engineer to build relational databases, AWS infrastructure, or backend microservices from scratch. --- ### 13.3 Sales & Onboarding Process ``` Step 1: Inbound Email (hello@frontend.supply with work email name@domain.com) ↓ Step 2: Cal.com Discovery Call Link Sent ↓ Step 3: 20-30 Minute Discovery Call (Review product, Figma, stack & fit) ↓ Step 4: Invoice Issued via US LLC (Wise / Mercury Wire Transfer) ↓ Step 5: 100% Upfront Payment Received ↓ Step 6: Workspace Onboarding (Slack Connect, GitHub, Figma, Linear) ↓ Step 7: Day 1 Kickoff (Codebase audit, roadmap setup, immediate execution) ``` - **Inbound Requirement**: Prospective leads must contact Doğukan from their **corporate/business email address (`name@company.com`)**. Personal `@gmail.com` or `@hotmail.com` inquiries are filtered to ensure genuine business intent. - **Onboarding Access Needed**: - **Slack Connect**: Direct channel between workspaces. - **GitHub**: Maintainer or Developer repository access. - **Figma**: View-only access is sufficient. - **Linear / Jira**: Standard member access for ticket tracking. - **Vercel** *(Optional)*: If client wants Doğukan managing preview and production deployments. --- ## 14. Comprehensive Lead FAQ & Scenario Playbook #### Q1: What makes Frontend Supply different from hiring a freelancer on Upwork? **A**: Freelancers bill by the hour, incentivize slow progress, juggle competing short-term gigs, frequently disappear or ghost, and require constant supervision. Frontend Supply gives you a dedicated senior engineer on retainer who acts like a full-time teammate, responds daily, proactively audits and leads your frontend, and delivers completed production-ready updates every week for a fixed price. #### Q2: What makes Frontend Supply different from hiring a full-time senior frontend engineer? **A**: A full-time senior engineer costs $10,000–$15,000+/month with taxes, healthcare, equity, and benefits, takes 2–3 months to hire, and creates long-term employment liability. Frontend Supply gives you senior-level fractional capacity and ownership for $4,500–$6,000/month on a flexible 4-week cycle that you can cancel anytime your workload eases. #### Q3: How does the delivery cadence work in practice? **A**: On the Basic plan ($4,500/mo), you receive **2 completed updates per week**. On the Pro plan ($6,000/mo), you receive **3 completed updates per week**. Each update is a production-ready batch squashed into your repository and deployed to a live preview URL. #### Q4: What happens if I don't have enough tasks ready for a week? **A**: Doğukan takes full ownership of the frontend. If you don’t have immediate tickets assigned, he will audit your codebase, identify architectural weaknesses, improve UI responsiveness, optimize performance, or refactor components. However, if you refuse to let him work autonomously and fail to provide assets, unused capacity for that period is forfeited. #### Q5: Can I pause my subscription if my team goes on vacation? **A**: No. Subscriptions run for a continuous 28 calendar days (4 weeks) and cannot be paused, similar to software subscriptions or apartment leases. #### Q6: Are there any refunds if I decide to cancel early? **A**: No. Frontend Supply has a strict no-refund policy. Once payment is made, capacity is locked for the entire 4-week period. #### Q7: Can I try the service before committing to a full month? **A**: Yes! You can book a **1-week paid trial** (1/4 of the monthly price: $1,125 for Basic, $1,500 for Pro). Your slot is strictly reserved during the trial. If you love the output, you transition into a fresh 4-week subscription. #### Q8: Can I upgrade from Basic to Pro in the middle of a month? **A**: Yes. You simply pay the prorated difference for the remaining days of your current 4-week cycle and immediately unlock Pro capacity (3 updates/week). #### Q9: What happens if Frontend Supply raises its prices in the future? **A**: You are protected by a **Lifetime Price-Lock Guarantee**. As long as your subscription remains continuously active, your monthly rate will never increase. #### Q10: Can you set up our Supabase database, AWS servers, or backend APIs? **A**: No. Frontend Supply specializes exclusively in frontend and UI engineering. Doğukan connects frontend applications to existing APIs, auth SDKs, and backend services, but does not build databases, write backend business logic, or manage cloud infrastructure. #### Q11: Can you work with our designer's Figma files? **A**: Absolutely. Doğukan is a UI and design system specialist with a Stack Overflow CSS Gold badge. He translates Figma designs into pixel-perfect, responsive React/Next.js/Vue code. #### Q12: Do you participate in daily standup meetings? **A**: No. To preserve uninterrupted focus for deep coding, Doğukan does not join daily standups. However, you can schedule up to one regular weekly sync and hop on quick 5–10 minute Slack huddles as needed. #### Q13: What payment methods do you accept, and can you fill out tax forms? **A**: Invoices are issued by a registered US LLC. Payments are accepted via international bank wire and ACH through Wise and Mercury. Doğukan provides signed W-8BEN forms for corporate compliance. #### Q14: How do I get started? **A**: Send an email to **hello@frontend.supply** from your company email address (`name@domain.com`) with a brief overview of your product and needs. Doğukan will reply with a Cal.com link to schedule a discovery call. --- ## 15. Contact & Online Presence - **Website**: [https://frontend.supply](https://frontend.supply) - **Direct Business Email**: `hello@frontend.supply` - **X (Twitter)**: [https://x.com/dogukanui](https://x.com/dogukanui) - **GitHub**: [https://github.com/dgknca](https://github.com/dgknca) - **Stack Overflow**: [https://stackoverflow.com/users/10698741/do%c4%9fukan](https://stackoverflow.com/users/10698741/do%c4%9fukan) - **Personal Website**: [https://dogukan.design](https://dogukan.design) - **LinkedIn**: [https://www.linkedin.com/in/dogukancavus](https://www.linkedin.com/in/dogukancavus)