ExampleClient Client Management
Three interconnected workflows for managing the ExampleClient freelance engagement with Client Contact.
Why This Exists
April 13, 2026: Client Contact escalated — checkpoints not delivered, hours burned without warning, code pushed without discussion. Nearly ended the relationship. Root cause: no daily updates, no proactive hour tracking, no decision trail. These workflows prevent that from happening again.
Client Profile
| Field |
Value |
| Client |
Client Contact, partner Partner Contact |
| App |
ExampleClient — anti-porn addiction, 8K+ downloads |
| Language |
Hebrew, casual, non-technical |
| Rate |
[RATE] (30hr blocks), overage [RATE] |
| Tools |
Linear (tickets), TestFlight/EAS (builds), WhatsApp (comms) |
| Priority |
SPEED above everything |
Workflows
| Workflow |
Trigger |
What it does |
| daily-update |
"draft Client Contact update", "client update", end of work day |
Draft structured async standup in Hebrew |
| decision-tracking |
Scope change, hour overrun, feature pivot, "log decision" |
Store WHO/WHAT/WHY/WHEN immediately |
| time-tracking |
Start/stop work, "track time", "log hours" |
Log human vs agent vs wall-clock time |
How They Connect
Time Tracking ──feeds──> Daily Update (hours worked today)
Decision Tracking ──feeds──> Daily Update (scope changes to mention)
Daily Update ──references──> both (pulls data for standup)
Hebrew Voice Rules (from 6 rounds of corrections)
These rules apply to ALL client-facing Hebrew output:
NEVER
- Start with name greeting on WhatsApp ("אלון," — just start with content)
- Include branch names, PR numbers, or git terminology
- Ask "should I...?" questions — state what you need
- List bugs in the message — defer: "מצאתי כמה באגים, אתעד ונעבור ביחד"
- Use technical jargon — "componentization" = "סידור וצמצום הקוד"
- Offer options that make the client work
- Use "מונה" when "מספור" is more natural
- Label bugs with technical terms — describe what the user will SEE
ALWAYS
- Status in first line (what's done)
- Collaborative framing: "ונעבור על זה ביחד"
- Max 2 options, never 3
- Casual tone: "אז ככה," to start explanations
- Explain WHY you waited: "חיכיתי תביקורת מכם"
- Reference their tools: "הטיקטים בלינאר" not "features"
- "ראיתי ש..." to show proactive tracking
- Specific ask > open question
- Group chat = plural verbs ("תבדוקו" not "תבדוק")
- For issues: [what client will see] + [what we'll do about it]
- "מעולה." alone is enough acknowledgment
- Comma not dash: "עוד דבר שמצאתי, המפתח..." not "עוד דבר שמצאתי - מפתח..."
Word Choices
| Wrong |
Right |
Why |
| חילצתי |
הוצאתי |
More natural |
| מונה |
מספור |
More natural for counter |
| שמהבהב |
שמראה |
Describe what it DOES not how it LOOKS |
| לשנייה |
לרגעים ראשונים |
Less precise, more natural |
| בכניסה |
לאחר התחברות |
More formal/correct for "after login" |
| מסיים עד סוף השבוע |
ממשיך היום |
Signal active work NOW |
Data Sources
- Voice corrections: BrainLayer
brain_search("user-correction hebrew voice-calibration alon")
- Entity:
brain_entity("Client Contact")
- Files: Obsidian
Clients/ExampleClient/
- Contract: Obsidian
Clients/ExampleClient/sprint2-approval.md
Critical Rule
Updates go to Operator's self-chat first, NEVER directly to the client. The draft is for Operator to review, edit, and send himself.
1---2name: example-client3description: ExampleClient freelance client management — daily updates, decision tracking, time logging. Use when drafting Client Contact updates, logging scope changes, tracking hours, or any ExampleClient client communication. Triggers: 'draft Client Contact update', 'client update', 'daily update', 'log decision', 'track time', 'example-client'.4---56# ExampleClient Client Management78> Three interconnected workflows for managing the ExampleClient freelance engagement with Client Contact.910## Why This Exists1112April 13, 2026: Client Contact escalated — checkpoints not delivered, hours burned without warning, code pushed without discussion. Nearly ended the relationship. Root cause: no daily updates, no proactive hour tracking, no decision trail. These workflows prevent that from happening again.1314## Client Profile1516| Field | Value |17|-------|-------|18| Client | Client Contact, partner Partner Contact |19| App | ExampleClient — anti-porn addiction, 8K+ downloads |20| Language | Hebrew, casual, non-technical |21| Rate | [RATE] (30hr blocks), overage [RATE] |22| Tools | Linear (tickets), TestFlight/EAS (builds), WhatsApp (comms) |23| Priority | SPEED above everything |2425## Workflows2627| Workflow | Trigger | What it does |28|----------|---------|-------------|29| [daily-update](workflows/daily-update.md) | "draft Client Contact update", "client update", end of work day | Draft structured async standup in Hebrew |30| [decision-tracking](workflows/decision-tracking.md) | Scope change, hour overrun, feature pivot, "log decision" | Store WHO/WHAT/WHY/WHEN immediately |31| [time-tracking](workflows/time-tracking.md) | Start/stop work, "track time", "log hours" | Log human vs agent vs wall-clock time |3233## How They Connect3435```36Time Tracking ──feeds──> Daily Update (hours worked today)37Decision Tracking ──feeds──> Daily Update (scope changes to mention)38Daily Update ──references──> both (pulls data for standup)39```4041## Hebrew Voice Rules (from 6 rounds of corrections)4243These rules apply to ALL client-facing Hebrew output:4445### NEVER46- Start with name greeting on WhatsApp ("אלון," — just start with content)47- Include branch names, PR numbers, or git terminology48- Ask "should I...?" questions — state what you need49- List bugs in the message — defer: "מצאתי כמה באגים, אתעד ונעבור ביחד"50- Use technical jargon — "componentization" = "סידור וצמצום הקוד"51- Offer options that make the client work52- Use "מונה" when "מספור" is more natural53- Label bugs with technical terms — describe what the user will SEE5455### ALWAYS56- Status in first line (what's done)57- Collaborative framing: "ונעבור על זה ביחד"58- Max 2 options, never 359- Casual tone: "אז ככה," to start explanations60- Explain WHY you waited: "חיכיתי תביקורת מכם"61- Reference their tools: "הטיקטים בלינאר" not "features"62- "ראיתי ש..." to show proactive tracking63- Specific ask > open question64- Group chat = plural verbs ("תבדוקו" not "תבדוק")65- For issues: [what client will see] + [what we'll do about it]66- "מעולה." alone is enough acknowledgment67- Comma not dash: "עוד דבר שמצאתי, המפתח..." not "עוד דבר שמצאתי - מפתח..."6869### Word Choices70| Wrong | Right | Why |71|-------|-------|-----|72| חילצתי | הוצאתי | More natural |73| מונה | מספור | More natural for counter |74| שמהבהב | שמראה | Describe what it DOES not how it LOOKS |75| לשנייה | לרגעים ראשונים | Less precise, more natural |76| בכניסה | לאחר התחברות | More formal/correct for "after login" |77| מסיים עד סוף השבוע | ממשיך היום | Signal active work NOW |7879## Data Sources8081- Voice corrections: BrainLayer `brain_search("user-correction hebrew voice-calibration alon")`82- Entity: `brain_entity("Client Contact")`83- Files: Obsidian `Clients/ExampleClient/`84- Contract: Obsidian `Clients/ExampleClient/sprint2-approval.md`8586## Critical Rule8788**Updates go to Operator's self-chat first, NEVER directly to the client.** The draft is for Operator to review, edit, and send himself.
EtanHey