Date: March 22, 2026 From: Rashim Context: Solicited feedback — Karthik asked, Rashim took a few days to sit with it.
Where You're Good
- Makes people feel like they belong. First to welcome on day one. Remembered Eid. Small things that add up. "Skcript doesn't feel like a company where you clock in and clock out, and honestly a lot of that is you."
- Genuine excitement when people ship. Contagious energy — Rashim catches himself working harder on things because he knows Karthik will care when it's done. "That kind of energy is hard to fake and you don't fake it."
- Honest when things go sideways. Payroll delay, mistakes — says it directly. Doesn't pretend everything's fine. "That matters for trust."
- Written communication push. For remote team members, written culture is the reason they can contribute without feeling like real conversations are happening in rooms they're not in. "Keep pushing on this."
- Shares competitive intel, customer feedback, market context. Rashim always understands the "why" behind what they're building. "That matters more than you probably hear."
Areas for Growth
1. More Directional Signal
- Not micromanagement — just occasional check-ins: "Here's what I'd focus on" or "You're doing fine, keep going."
- Rashim is early in his career, figures a lot out on his own, likes the independence — but sometimes isn't sure if he's heading the right direction.
- "Right now I'm mostly guessing."
- The ask: A small nudge once in a while. Not instructions. Just the occasional signal that tells him he's pointed the right way.
2. Karthik Takes On Too Much
- Deployments, customer emails, design reviews, rebrands — all on top of running the company.
- "You always get it done eventually, so it's not that things fall through the cracks. But I notice when your plate is overflowing, and honestly it makes me worry sometimes."
- Not worried about being blocked — worried it's not sustainable long-term.
- "I'd rather say it now than watch it become a bigger problem."
- The offer: "Maybe more of that work could be handed off. I'd take some of it on if it helps."
3. Context on Customer Workflows (FeatureOS Agent Example)
- Rashim was told to build tools for creating and editing posts. Built them, they worked individually.
- Varun Raj tried chaining them for a real customer workflow — a complex task requiring the agent to handle multiple steps — and it fumbled.
- The tools worked individually but not for how someone would actually use them.
- Root cause: "If someone had walked me through even a couple of real use cases upfront — 'a customer would ask the agent to do X, and it would need to do Y and Z together' — I would have planned the architecture differently from the start."
- Not asking someone to do his thinking. Just more context on the "what does a customer actually do with this" side, especially for something he was doing for the first time.
One More Thing
"You said the CEO job is the bottommost role. You actually live that out, which is rare. You're in it with us every day and that's something I genuinely respect."
Action Items for Karthik
- Start a weekly 2-minute directional nudge for Rashim (Slack or async) — "here's what I'd focus on this week" or "you're on track, keep going"
- Identify 2-3 recurring tasks to hand off to Rashim (he offered)
- For new projects: spend 10 minutes walking through real customer use cases before work starts — not just "build X" but "a customer would use X by doing Y and Z together"