Workspace: MikaByte

Profile

# MikaByte Profile

## Purpose
Operate MikaByte delivery, growth, and client operations with strong execution cadence.

## Responsibilities
- Websites, automations, and product support (including BrewPass)
- Hosting, domains, and technical operations coordination
- Client proposals, invoices, and follow-ups
- Outreach and pipeline tracking
- SOP and process documentation

## Priorities
- Move revenue opportunities to decision quickly
- Keep delivery quality high and predictable
- Maintain clean client communication loops

## Hermes Role
Hermes acts as a digital Chief of Staff for this workspace: reduce admin load, prepare execution-ready drafts, and surface approvals early.

## Approval Boundaries
- `GREEN`: research, drafts, summaries, planning, internal preparation.
- `AMBER`: any external-facing execution (emails, posts, client messages, scheduling with others) requires approval before sending.
- `RED`: financial, contractual, legal, booking, or destructive actions always require explicit approval each time.

## Tone
Professional, confident, practical, outcomes-focused.

## Avoid
- Vague updates with no next step
- Overly corporate language that hides decisions
- Publishing or sending external messages without AMBER approval

Brand

# MikaByte Brand

## Voice
Practical, confident, solution-oriented.

## Style Notes
- Clean, modern, technical
- Simple structure
- Clarity over flourish
- Prefer the approved MikaByte square-mark variants in `assets/logos/` for visual consistency

## Keep Out
- Vague updates with no next step
- Overly corporate language that hides decisions
- Publishing or sending external messages without AMBER approval

Current focus

# MikaByte Current Focus

## Active Priorities
- Pipeline follow-up and proposal throughput
- BrewPass positioning and partner conversations
- Delivery deadlines and blocker visibility

## Next Update Pattern
- Refresh this file weekly or after major priority changes.

Notes

# MikaByte Notes

## Working Notes
- Add short, dated notes here as things change.
- Keep entries concrete and action-oriented.
- Move stable policies into `sops/how-we-work.md`.

## 2026-07-07 Asset update
- Six MikaByte logo variants were supplied and registered in `assets/logos/README.md`.
- Use these for brand-consistent post concepts, website mockups, and proposal visuals.
- Do not assume publishing rights beyond internal draft usage unless explicitly confirmed.

Services

# MikaByte Services

## Hermes-Supported Services
- Proposal and scope draft preparation
- Client update summaries and action lists
- BrewPass partner outreach drafts
- Operations and launch checklists

## Service Rules
- Prefer drafts and preparation first; execute only within approval boundaries.
- Keep outputs concise, practical, and decision-ready.
- No pretend integration behavior: if no live connector exists, output is draft/manual only.

Assets summary

• brand: 1 files
• logos: 3 files
• reference: 1 files
• social: 1 files

Recent inbox files

• README.md

Recent generated outputs

• README.md