Symph Reorganization · 2026

The Current

16 years in. A new model. Not because we're broken — but because the tools changed and we'd be foolish not to. This is the full story of what changed, why it changed, and what your day actually looks like now.

What changed ↓ What's my day now? What are we selling?
The Shift

What changed, and why

This isn't a rebrand. It's a fundamental rethink of how we create value — forced by a reality that was always coming, just faster than anyone expected.

Before · The Old Symph
  • A project comes in. A team is assembled: PM, designer, developer, QA, account manager.
  • The developer writes code all day, every day. That's the job. Jira ticket → code → PR → merge.
  • A custom project takes 3–6 months. That's the timeline you quote. That's what the client expects.
  • Revenue is time. More developers = more hours billed. Hours × rate = revenue.
  • You know who you are: "I'm a dev." "I'm a designer." Identity is your title.
  • Growth meant getting promoted within your lane — Junior → Mid → Senior → Lead.
  • Clients wait. Pipelines fill. Timelines slip. That's just how it works.
  • Custom software is expensive because it takes human time. 48,000/day per person.
Now · The New Symph
  • AI scaffolds the work. Agents write first drafts. Humans review, refine, and judge quality.
  • A dev might spend their day in Growth automating outreach — not writing product code at all.
  • That same custom project? We can ship it in 1 month. Same quality. Fraction of the time.
  • Revenue is outcomes and volume. Faster delivery means more clients served, more deals closed.
  • You are a problem-solver who happens to have a skill. Your current describes where that skill creates the most value right now.
  • Growth happens in depth, breadth, and influence — not titles.
  • Speed is our moat. We respond to signals, not backlogs. Movement happens same-day.
  • We can price competitively and still win because our cost structure changed. Time is on our side.

The honest version: AI didn't take your job. It changed what your job is. A developer who only codes is less valuable than a developer who can code, automate, and understand growth. The reorg is not a demotion — it's us betting on your full capability, not just your most obvious one.

Start Here

You've been assigned
a home current

Every person at Symph now has a home current — the current where you'll spend 60–80% of your time and develop mastery. Think of it as your base, not your boundary.

Your initial assignment is based on where we believe your skills will create the most impact in this new model. It's a starting point, not a permanent label. As we learn what works — as the organization reads signals, builds new muscles, and discovers what AI-native Symph actually looks like — your home current can and will evolve. Nobody fully knows what we need yet. We'll figure it out together, in motion.

🧭
Your assignment is a starting position
Leadership has placed each person based on where they see the strongest skill-to-impact fit. This isn't a promotion, demotion, or commentary on your past work. It's a bet on where you'll thrive in the new model. If it doesn't feel right after you've lived in it, we adjust.
🔄
You will move between currents
When a current needs help, it posts a signal. You might get pulled into another current for a day, a week, or a sprint. Being pulled is not punishment — it's a sign your skills are recognized beyond your home. Your home current always takes you back.
📈
Growth looks different now
There's no ladder from Junior to Senior to Lead. Growth happens in three dimensions: depth (becoming essential in your current), breadth (contributing to adjacent currents), and influence (shaping how the current works). The marker isn't a title — it's the scope of what you're trusted with.
Skills define you, not titles
A developer can home in Growth. A designer can home in Taste. Your current describes where you apply your skills to create the most impact. We're not erasing what you know — we're putting it where it matters most right now.
6 Currents, First Principles

The Six Currents

Instead of departments, we organize by currents — the core functions of the organization. Each current defines a type of work, not a type of person. Click any current to see what life looks like inside.

Day in the Life

What does your day
actually look like?

The question everyone's asking but nobody's answered clearly. Here it is. Select your role and see what a real day looks like in each current you might be assigned to.

Developer · Build Current
Home in Build — your craft meets AI output

You used to get a Jira ticket and code. Now you get an agent scaffold and you decide what's good enough and what needs your judgment. The volume of work is higher. The nature of work is different.

  • Morning · 8–10 AM
    Review overnight agent output
    The agent scaffolded a feature while you slept. Pull the branch. Does it work? Does it work well? Flag what needs human judgment — edge cases, security concerns, interactions that feel off. This is the highest-leverage hour of your day.
  • Mid-morning · 10 AM–12 PM
    Refine, customize, ship
    The parts of the scaffold that needed craft — you handle those now. A responsive layout that the agent got wrong. A state management pattern that doesn't scale. An animation that needs to feel right. This is where your taste as a developer matters most.
  • Afternoon · 1–4 PM
    Document, teach, expand the frontier
    Write the pattern so the agent handles this next time. This is the work that compounds. Every 30 minutes you spend documenting saves you 3 hours next sprint. The best day in Build is when something you did manually last week is now fully automated.
  • End of Day · 4–5 PM
    Signal check + Friday retro prep
    Check the scoreboard. Is there a signal from another current that needs your skills? Has the queue backed up somewhere? Note one thing that was manual this week that shouldn't be manual next week.
Win of the day: Something that used to take a week shipped in a day. And the agent now knows how to do it.
Metric: Ship time ↓
Metric: Agent autonomy ↑
Metric: Customization speed
Developer · Growth Current
Your code makes the pipeline move — not the product

You are not here to build products. You are here to build the machine that gets people to pay for them. Your code today might be an outreach automation, a lead enrichment script, a landing page variant, or a conversion tracking dashboard. If it moves the pipeline, it counts.

  • Morning · 8–9 AM
    Growth metrics check
    Check conversion rates, email open rates, pipeline movement from yesterday. Where are people dropping off? What experiment ran overnight? This is your daily orientation — the scoreboard tells you where to work today.
  • Mid-morning · 9 AM–12 PM
    Build growth tooling
    The outreach team is manually enriching leads from LinkedIn. You write a script that does it in 10 minutes instead of 3 hours. The Product Growth Lead needs a landing page A/B test set up. You build it. This is coding — but in service of the pipeline, not the product.
  • Afternoon · 1–3 PM
    Experiment, analyze, iterate
    Growth is a science. Run the test. Analyze results. Feed the Product Growth Lead with data so they can make better decisions on messaging and targeting. You're not a marketer — you're the infrastructure that makes marketing scalable.
  • Afternoon · 3–5 PM
    Pipeline contribution report
    What did you ship today that will move leads tomorrow? Document it. Share results with the Product Growth Lead. If your pipeline number didn't move this week, that's the conversation — not a blame game, but a troubleshooting session.
Win of the day: The outreach automation you built added 20 qualified leads to the pipeline without the sales team lifting a finger.
Metric: Qualified leads generated
Metric: Pipeline 3x
Metric: Conversion rate ↑
Developer · Build Current, Client Block (Agency Delivery)
Assigned to a hypercustom client — think NAP Solutions

This is the closest thing to how we used to work — but faster, and with more direct client contact than you're used to. You don't wait for a PRD to be handed down. You're in the room (or on the call) with the client, understanding what they need, then building it. Your PM is there, but they're a coordinator, not a filter between you and the client.

  • Week 1 · Kickoff
    Client kickoff — you are in the room
    No more receiving a PRD two weeks after kickoff. You are in the client kickoff. You hear the requirements directly. You ask the technical questions. You understand what they actually need, not what got lost in translation from PM to developer. NAP Solutions has been waiting — the kickoff happens immediately.
  • Daily · Sprint Rhythm
    Build → Demo → Clarify → Build
    You ship working code within days, not weeks. You demo it directly to the client. You get feedback in real-time. The loop is tight. AI scaffolds the boilerplate; you handle the complexity and the judgment calls. The PM keeps the timeline and budget visible so you can focus on building.
  • Throughout · Direct client communication
    You talk to the client — not just through the PM
    If you have a technical question, you ask the client directly. If you're making an architectural decision that affects scope, you flag it to both the PM and the client. This is not new — this is how good developers have always worked. The reorg just makes it explicit.
Win of the engagement: NAP Solutions sees working code in week 1. The old Symph would've been in discovery. 3M pesos, collected in 1 month instead of 6.
Metric: On-time delivery
Metric: Client satisfaction
Metric: Revenue collected on schedule
Designer · Build Current
Making agent output worth paying for

The agent can scaffold UI. What it can't do is know whether it's good. That's you. Your eye for hierarchy, spacing, emotion, and trust is the difference between something that ships and something that converts.

  • Morning
    Review agent-generated screens
    The AI generated 10 screens overnight. You open them. Some are 80% there. Some miss completely. Your job is to know the difference — quickly — and direct what gets fixed versus what gets thrown out.
  • Mid-morning
    Craft the 20% that matters
    The hero section needs emotional weight. The onboarding flow needs to feel effortless. The dashboard needs to communicate trust at a glance. This is what you spend your creative energy on — the moments that make someone say "this feels premium."
  • Afternoon
    Build the design system — teach the agent
    Document the patterns you just created. Write prompts that will help the agent generate better UI next time. Create component libraries. The more you systemize your taste, the more you multiply yourself across every product the agency ships.
Win of the day: 10 screens reviewed, 8 approved with minor tweaks, 2 rebuilt from scratch. The agent will get the 8 right next time.
Metric: Design approval rate
Metric: Time from scaffold to ship
Designer · Growth Current (Creatives Role)
You own how the brand looks and whether it converts

You're not in a design studio anymore. You're in a growth engine. Every visual you create has one job: move a prospect closer to paying. Beauty without conversion is a hobby. You are accountable to both.

  • Morning
    Channel performance check
    Check Instagram, LinkedIn, TikTok, Facebook metrics. What performed yesterday? What flopped? The Creatives Lead wants a read — you bring data, not excuses. If engagement is flat, you already know what you're testing today.
  • Mid-morning
    Create content aligned to the Product Growth Lead's direction
    The Product Growth Lead defined the message this week: "Clocklane helps SMBs reclaim 10 hours a week." Your job is to make that land visually on every platform — in the format, language, and visual style each audience expects. You adapt, not copy-paste.
  • Afternoon
    Publish, coordinate, review
    Posts go live. No platform should ever go dark — that's on you. You review what your team produced if you're a Creatives Lead. You flag anything off-brand. You ensure the Sales team has the assets they need to walk a client through a pitch.
Win of the day: A post you designed drove 3 inbound inquiries that are now in the Sales pipeline. That's your KPI moving.
Metric: Qualified leads from channels
Metric: Engagement rate per platform
Metric: Content calendar adherence
Designer · Taste Current
You are the quality bar everyone else calibrates to

Nothing ships without Taste. Not a landing page. Not an outreach email. Not a product UI. You are the final gate — and you're not just saying "yes" or "no." You're saying why, in terms specific enough that the agent or human can improve.

  • Morning
    Review queue — is this remarkable or just acceptable?
    The queue has 12 items: 4 marketing creatives, 3 product UI screens, 2 outreach emails, 3 client-facing documents. You review each. "Acceptable" gets rejected. "Remarkable" ships. The bar is not "does it work." The bar is "would someone tell a colleague about this?"
  • Mid-morning to Afternoon
    Articulate the feedback — teach, don't just reject
    Every rejection comes with a specific explanation: "The hierarchy is wrong — the CTA is competing with the headline for visual weight. Move it below the subhead and give it 40% more contrast." This feedback trains the human and, eventually, the agent. Vague feedback is wasted effort.
  • Weekly
    Calibrate — what does "good" mean this week?
    Taste isn't static. Trends shift. Client expectations evolve. You hold a weekly calibration: here's what we approved, here's what we rejected, here's what we got wrong in our own judgment. The standard is always moving up.
Win of the day: Your specific feedback on a rejected landing page led to a redesign that converted 3x better in the first week.
Metric: Rejection rate ↓ (agents improving)
Metric: Taste-to-revenue correlation
Project Manager · Build Current (Agency Delivery)
You coordinate speed — not control information flow

In the old model, the PM was the bridge between client and developer — information passed through you in both directions. In the new model, you still coordinate, but the developers talk directly to the client too. Your job is to keep the machine moving fast, on budget, and on time. Not to own the information.

  • Morning
    Scoreboard review — where are we vs. where we should be?
    Pull up the project timeline. For NAP Solutions: are we on track for week-1 delivery? Are blockers visible? Is the client expecting something we haven't communicated about? Your first hour is visibility — not meetings.
  • Mid-morning
    Client sync + builder coordination
    Brief client check-in: status, what's ready to demo, any new requirements. Then back to the team: what do the builders need to unblock? Are they stuck on a requirement? Do they need access to a client system? You clear paths — you don't carry bricks.
  • Afternoon
    Budget + scope vigilance
    The client mentioned a new feature in passing this morning. Is that in scope? If not, how do you handle it without damaging the relationship? This is where PM judgment matters: protect the team's time AND the client relationship. These are not opposites.
  • End of Day
    Tomorrow's readiness
    What does the team need tomorrow to keep moving? Are assets ready? Are approvals pending? Set up tomorrow for zero-friction mornings. A PM's success metric is how rarely their builders are blocked.
Win of the day: Builders never waited. Client always knew where we were. Project 2 days ahead of schedule.
Metric: On-time delivery rate
Metric: Budget adherence
Metric: Client satisfaction score
Metric: Blocker resolution time
Growth Current · Decoded

The roles inside Growth
and how they connect

Growth is the largest current because the bottleneck is never building — it's selling. Here's how each role in Growth works and what you're accountable for.

🎯
Product Growth Lead
Strategy, offering, and outcome ownership

You own the product's success in the market. If nothing is selling, accountability starts with you. You are the connective tissue between Build (what we're making), Creatives (how we're presenting it), and Sales (who's closing it).

  • Drive strategy end to end — brand voice, offering, go-to-market, pricing, landing page
  • Own the offering inside and out. Know exactly what we're selling and ensure messaging is consistent across all platforms
  • Define the ideal client profile — who is right for this product, and who isn't
  • Collaborate with Build to ensure we're building exactly what needs to be shipped
  • Keep the product always demoable and pitch-ready — live demo site + updated pitch deck at all times
  • Enable Sales: research the target market, provide objection-handling frameworks, make sure Sales can close
  • Demo the product to the internal team regularly so everyone knows what we're selling
  • Work with Symph clients and Build to create fluid (Encore) versions of existing apps
  • Own the growth outcome. No traction? That starts with you.
How success is measured
Quality and consistency of creative output · State of the product (demoable, pitch-ready) · Qualified leads generated by the team assigned to you · Conversion of product to revenue
📞
Sales Team
Close what the Product Growth Lead sets up

You don't define the offering. The Product Growth Lead does. Your job is to take that offering — with its pitch deck, demo site, and target market — and close deals. Proactive, not passive.

  • Run outbound prospecting — research and reach out to the target market defined by the Product Growth Lead
  • Close inbound leads quickly — respond fast, qualify, move prospects through the pipeline efficiently
  • Manage existing accounts — stay in contact, find upsell opportunities, confirm they're getting value
  • Know the product well enough to sell it — attend demos, understand the pitch deck, walk prospects through the offering confidently
  • Give the Product Growth Lead market feedback — what objections are coming up? What's landing? What isn't? This is how the offering gets sharper
  • Own your pipeline — if it's dry, that's on you to flag and fix, not wait for it to be noticed
How success is measured
Number of closed deals · Pipeline velocity · Conversion rate from qualified lead to closed
🎨
Creatives Lead
Own the brand presence. Own the growth metrics.

You own how the product looks and sounds on every channel — Facebook, Instagram, LinkedIn, TikTok, Reddit, X. And you own the numbers. Creative without performance accountability is not enough.

  • Own the product's creative presence across all channels — no channel goes dark, ever
  • Manage your team of creatives — assign work, review output, give feedback, hold quality
  • Lead at least one platform directly while ensuring the rest are covered
  • Maintain brand and message consistency across all channels — aligned with Product Growth and Build
  • Create and manage all publication materials — print, digital collateral, branded assets for sales and events
  • Own data analytics, ad optimization, audience targeting, conversion metrics — creative without performance is decoration
  • Maintain a content calendar — every platform, consistent schedule, no gaps
  • Track performance per channel and adjust creative direction based on data, not intuition alone
  • Coordinate with Sales when they need assets; coordinate with Product Growth on campaigns
How success is measured
Number of qualified leads generated through creative channels · Engagement and reach per platform · Pipeline contribution from organic + paid
✏️
Creative (Individual Contributor)
Own your platform. Own your numbers.

You are assigned one or more platforms. Those platforms don't go dark. They perform. The content you put out represents the brand — don't ship anything you wouldn't be proud to show a client.

  • Own your assigned platform(s) — know what performs, what the audience expects, what formats work
  • Post consistently — follow the content calendar, no gaps
  • Align all content with the Creatives Lead direction — when in doubt, ask before posting
  • Track your platform's performance — bring insights and recommendations to the Creatives Lead, not just posts
  • Flag issues early — falling behind, messaging confusion, performance drops — raise it immediately
  • Support the team — if another creative needs help or a platform needs extra coverage, step up
How success is measured
Qualified leads attributed to your platform(s) · Engagement rate · Consistency of posting schedule

How Growth roles work together: The Product Growth Lead sets the message and the target. The Creatives Lead turns that message into content across every channel. The Creatives execute on their platforms. Sales takes qualified inbound and outbound and closes. The Product Growth Lead and Creatives Lead QA each other's output — no separate QA layer needed. It's a tight loop: strategy → content → leads → closed.

The Portfolio Rule

Before we build a team around it,
talk to 50 customers first

50
The Validation Gate
Before a new product can justify a full team — Product Growth Lead, Creatives Lead, Creatives, Sales — you must have talked to 50 customers and demonstrated real validation. Not internal excitement. Not a well-designed deck. Actual conversations with the market that confirm people have this problem and are willing to pay.

This protects the organization. We cannot afford to keep adding to our portfolio while existing products chase traction with no team behind them. Every product that gets a team is a bet. Bets require evidence.

50 conversations. Real demand. Then we build the team.
What We're Selling

Four ways Symph
makes money now

The reorg isn't just an internal restructuring. It unlocks a completely different range of clients and deal sizes. Here's what we offer — and why each one exists.

OFF-THE-SHELF · B2B PRODUCTS
01
The Symphony Suite
Six products. Six problems. Each has a defined ICP, a team behind it, and a clear metric. Growth drives leads. Sales closes deals. Build ships improvements. Measured by qualified leads and closed deals.
  • Alignly — HR and people alignment
  • Clocklane — Time and scheduling intelligence
  • Encore — Client relationship management (includes Worklane)
  • Overture — Business insights and analytics
  • Vector — Project and portfolio management
  • ContentVane — Content operations
HYPERCUSTOM · AGENCY
02
The Agency
Custom software — but shipped in weeks, not months. The same thing we've always offered, packaged differently because we can deliver it faster. PM + Builders team. Client is in the room from day one. Three pricing models depending on what the client needs.
  • One-time build — Pay once, own the system (NAP Solutions)
  • Flexi subscription — Pay monthly, keep evolving (Johndorf)
  • Per system / month — Right-sized for small teams (Fort Tektron)
RESELLER · PARTNERSHIPS
03
Reseller & Partnerships
We resell GWS, Josys, and GCP — earning margins on every seat and license. As partnerships deepen, we earn incentives and bonuses beyond the margins. This year alone, the GCP deal generated funding separate from margin income.
  • Google Workspace (GWS) — Productivity suite resell
  • Josys — SaaS management platform
  • GCP — Cloud infrastructure with partnership incentives
PEOPLE · CONSULTANCY
04
Staff Augmentation & Consultancy
We lend our people — but not just developers and designers anymore. PMs like Ranil and Chiefs like Dave now operate as consultants. The person is deployed on client blocks, billing their time directly. Higher rates. Broader scope.
  • Technical augmentation — Developers and designers embedded in client teams
  • Design augmentation — Creative direction and UI/UX leadership
  • PM augmentation — Project coordination for client organizations
  • C-suite consultancy — Strategic advisory from Symph leadership
Agency Pricing · Real World

Three clients. Three models.
All of them work.

There's no universal price point for hypercustom software. The right price is what the client says yes to — structured so Symph doesn't lose. Here's how three real deals look.

NAP SOLUTIONS · ONE-TIME BUILD
Pay once, own it
Enterprise client. IT team of 10. Full scope crawler system. They know exactly what they need. The old Symph would take 3–6 months. The new Symph delivers in 1 month with AI-accelerated tools. Client → formal kickoff → builders talk directly to client → ship.
₱3M
Collected in 1 month vs. 3–6 months
JOHNDORF · FLEXI SUBSCRIPTION
Pay monthly, keep evolving
300 people. Don't know the full scope yet. They're smart — they know forcing a one-time spec now means missing everything they'll discover later. So they subscribe. We keep building as they grow. Two years guaranteed. Option to buy the system outright after.
₱6.5M
Guaranteed over 2 years. ₱900/user/month × 300
FORT TEKTRON · PER SYSTEM
Right-sized for small teams
5-person construction company. Everything on Google Sheets. Per-user pricing doesn't work at this scale — it can't cover hosting, AI credits, and maintenance. Per system per month does. They want 3 systems. Each ships in a week.
₱45K+
Per month · 3 systems × ₱15K · Scales with users

The pricing isn't fixed. It's discovered through the conversation. Who's the decision-maker? What model hurt them before? What would they say yes to without us losing money on the promise? The reorg allows us to play the big-fish game AND the volume game — because we can ship fast enough to serve both. 100 companies paying ₱45K/month is ₱4.5M/month. That's the volume play. One NAP Solutions is the big-fish play. We're doing both.

The Operating Model

How all currents
co-exist and collaborate

Currents aren't islands. Every current depends on every other current to function. Here's how the connections actually work in practice.

GROWTH → BUILD
Briefs, not bottlenecks
Growth identifies what the market needs. Build builds it. Product Growth Lead works directly with Build to ensure what's being shipped is what can be sold. No delay, no game of telephone.
BUILD → TASTE
Nothing ships unreviewed
Every client-facing output from Build passes through Taste before it reaches the client. Taste doesn't block — it accelerates quality. A fast review catches what would take a week to fix post-launch.
TASTE → AGENT
Feedback becomes capability
When Taste rejects something and explains why, Agent current captures that feedback to improve the AI output next time. Taste's judgment becomes Agent's training data. The system gets smarter every week.
OPS → EVERYONE
The safety net that enables speed
Ops watches the humans, not the work. Burnout, conflict, pace issues — Ops catches them before they become crises. If you're running at 120% for two weeks, Ops intervenes. This is what makes sustainable speed possible.
J&A → EVERYONE
The signal reader and decision maker
Judgment & Accelerate watches the scoreboard. When something is stuck — a product not gaining traction, a current overwhelmed — J&A makes the call: kill it, scale it, pivot it, or send reinforcements. Hours, not days.
AGENT → BUILD + GROWTH
Multiplies everyone's output
Agent current builds the tools that make Build and Growth faster. When Growth finds a manual bottleneck, Agent automates it. When Build identifies a repeatable pattern, Agent encodes it. Every current gets faster as Agent improves.
The Operating Rhythm

How signals replace assignments

In the old model, a manager assigned you work from a backlog. In the current model, the system generates signals — and people and resources flow toward them.

1
Signals surface
A client request, a venture stalling, a queue backing up, a quality failure. These are signals. They appear on the scoreboard — visible to everyone, in real time.
2
People respond
When a current needs help, it posts the signal. People with capacity and relevant skills can volunteer. If nobody does, Judgment & Accelerate makes the call. Movement happens same-day.
3
The system learns
Every signal, every response, every outcome teaches the organization. Friday retros surface patterns. Assumptions get tested. The currents get smarter — not just the people.
What Makes It Work

Learning Disciplines

Structure alone doesn't make us a learning organization. These five practices do. Without them, currents are just departments with different names.