Fractional CIO & Strategic Advisor | Helping Non-Technical Leaders Make Technical Decisions | Scaled Orgs from $0 to $3B+

Strategic IT Leadership for Growing Companies

Helping non-technical founders and small business leaders scale without getting slowed down by their own systems

The Problem
Most companies don’t fail because they dream too small.
They fail because their technology trips them up before they ever hit full speed.

Systems that don’t talk to each other

Vendors that overpromise and underdeliver

Teams that pull in different directions

Operational chaos hidden behind "we’ll fix it later"

Growth without fundamentals isn't a shortcut—it's a detour. Real business expansion is about building systems that scale with integrity, not just adding layers of complexity to a shaky core.

The Outcome
I help you build a stronger, smarter, simpler technology foundation — one that scales with your business, not against it.

✅ Faster operations
✅ Smarter use of tools and teams
✅ Fewer expensive mistakes
✅ A clear, flexible roadmap for growth
✅ More time spent leading — less time fighting fires

My Approach
I’m not here to sell you systems you don’t need or waste months writing strategy decks nobody reads.

I’m here to help you:

Fix what’s broken (before it costs you real money)

Align your people, process, and platforms (so they work together, not against each other)

Build momentum you can actually feel (and measure in real-world results)

I bring 30 years of hands-on experience building and scaling IT in organizations that grew from to over $3B — many times as the very first IT hire, often leading global distributed teams.

What you get is simple:
Real strategy. Real execution. Real growth.

No bloat. No buzzwords. No bureaucratic nonsense.

Services
Fractional CIO Leadership
Part-time executive leadership to align your tech and business strategy, manage vendors, and build internal capabilities without hiring a full-time CIO.

Project Rescue and Turnaround
When critical projects stall, I step in to realign teams, simplify the chaos, and deliver results.

Vendor and System Sourcing
Find the right systems and partners that fit your business — not someone else’s template.

Strategic IT Roadmapping
Clear, practical roadmaps that connect today’s actions to tomorrow’s growth.

Who I Work Best With
Founders and business leaders who:

Are serious about scaling

Know tech is crucial but don’t want to live inside it

Value momentum over perfection

Want a partner who talks business, not just tech

Ready to Clear the Bottlenecks and Build What's Next?
Let's start with a simple conversation.
No sales pitch. Just clarity on where you are — and what’s possible next.

Phillip R. Kennedy

The VP forwarded the CEO's angry email to the whole engineering team at 9:47 PM on a Thursday. 

Daniel's manager replied-all at 9:48: "I'll handle this. Everyone log off."

Twelve seconds. Two completely different leaders.

The CEO's email was four sentences. A client's integration broke during a routine deployment. The client called the CEO directly. The fourth sentence: "I need to understand who is responsible."

The VP read it and clicked Forward. Added the entire engineering distribution list. Twenty-three people. Two words at the top: "See below."

No context. No plan. Just a CEO's anger, amplified to two dozen engineers on a Thursday night, most of whom had nothing to do with the deployment.

Daniel was brushing his teeth when his phone buzzed. He'd been at the company four months. He'd worked on a small piece of the integration three weeks earlier. Close enough to wonder. Close enough to lose sleep.

His shoulders went up. He started mentally composing a defense for code he'd written at 2 PM on a random Tuesday.

Then his phone buzzed again. 9:48.

"I'll handle this. Everyone log off."

Seven words. No exclamation point. No performative urgency. Just: this is not your problem tonight. It's mine.

James fixed it by 11:30. Configuration issue. Not a code defect. Nobody on the team caused it.

The next morning, James emailed his team: "Issue resolved. Config problem. Nothing any of you shipped caused this. If last night's email stressed you out, that's worth a conversation. My door's open."

Daniel saved that message. Not because it was eloquent. Because it was the first time a manager acknowledged that an internal communication could cause harm, and took ownership of it.

The VP forwarded blame at the speed of a click. James absorbed it in twelve seconds.

Same crisis. Same night. Two completely different engineering cultures.

Your team already knows which one you are.

♻️ Repost if you've had a manager whose first instinct was to protect the team, not forward the pressure 

➕ Follow me (Phillip R. Kennedy) for more on engineering leadership that absorbs the hit instead of passing it down

I've spent 30 years watching what great technical leaders actually do.

Almost none of it looks like leadership on paper.

18 things I've seen the best ones do:

1. Say "I don't know" out loud so the team learns it's safe to say it too.

2. Kill a meeting to protect four hours of uninterrupted build time.

3. Put a junior engineer on the project everyone said she wasn't ready for. Then quietly clear the path.

4. Sit in the architecture review and ask the quiet person in the back what they think. Then actually wait for the answer.

5. Walk into a budget meeting and make technical debt visible to executives who only see features shipped.

6. Recognize the engineer who prevented the outage. Not just the one who fixed it.

7. Take the call from the angry stakeholder so the team can keep building.

8. Fight for an infrastructure investment that won't show results for six months. Then fight again when someone tries to cut it in Q3.

9. Tell their best engineer "you should interview for that role" before she'd ever considered leaving the team.

10. Share their own worst production mistake in a retro. Watch the room exhale.

11. Push for a promotion before the engineer asks. Then build the case so well it's undeniable.

12. Translate a forty-five minute technical explanation into two sentences a CFO can act on. Without losing what matters.

13. Block the fourth "urgent" request in two weeks. "Urgent" is not a strategy.

14. Pair a twenty-year veteran with a six-month hire. Tell both of them they're going to learn something.

15. Turn "this is broken" into "what would good look like?" Same facts. Completely different energy.

16. Advocate for sustainable pace when everyone above them is performing urgency.

17. Create space for exploration that might not ship anything. Then defend it when someone asks for the ROI.

18. Remember that the job was never to be the smartest person in the room. It was to make the room smarter.

None of this shows up on a dashboard. Most of it never gets recognized in a performance review.

But the engineers remember. And they become leaders who do the same things.

That's how you scale more than systems.

♻️ Repost if you've had a leader who did one of these and it changed your trajectory 

➕ Follow me (Phillip R. Kennedy) for more on technical leadership that builds people, not just products

He texted me eighteen months after leaving the company. 7:32 AM on a Tuesday. "Congrats on the promotion. You earned it."

He had zero organizational reason to care.

James had been my CTO for three years. Left to start his own company. Most former bosses disappear when the org chart changes. Within a month, the relationship becomes a LinkedIn connection you scroll past.

James never did that.

When I got stuck on an architecture decision after he'd gone, I almost didn't reach out. He replied in twenty minutes: "Coffee Thursday?" Asked three questions that reframed the problem. No lecture. No "remember who helped you" energy.

When a product manager kept changing requirements mid-sprint, James said something I still use: "Your job isn't to stop the changes. It's to make the cost visible to the people requesting them."

When I left for a startup, most of leadership went quiet. That silence tells you which relationships were real. James responded in an hour: "Exactly the right move. Need references?"

The promotion text came a year later. His own company, across the country. My career had zero impact on his.

I've had many managers. Most competent and forgettable. James is the only one whose influence outlasted his badge access.

He never managed from the org chart. The authority was incidental to the relationship. When the authority left, the relationship didn't.

Most leaders aren't this way. Not because they're bad people. Because organizations reward transactional leadership. When someone leaves, the incentive to stay connected disappears.

Leaders who stay were always outside that system. They invested in the person, not the role.

The test that matters more than any review: would people who used to work for you still take your call? Not because you can help them. Because it was never about that.

♻️ Repost if you've had a leader whose influence outlasted their title

➕ Follow me (Phillip R. Kennedy) for more on leadership that survives the org chart

She said she was "doing fine" and "learning a lot." Two weeks later she put in her notice.

I'd asked all the right questions. How are you settling in? Anything blocking you?

Surface-level questions get surface-level answers. And surface-level answers hide problems until they become resignation letters.

That exit taught me first 1:1s aren't introductions. They're the moment you earn honest communication or guarantee you'll never get it.

Most leaders fill that meeting with org charts and project updates. Nobody gets uncomfortable. Nobody learns anything.

After thirty years, here's what actually surfaces truth:

"Walk me through the last time you dug into someone else's code." Tells you more about team culture in three minutes than any survey. Listen for colleagues who help vs. territory that's guarded.

"What's the most frustrating part of getting your work done here?" Not "any concerns?" That gets "everything's great." Ask what frustrates them, then sit in the silence. The pause tells you whether honesty feels safe.

"When you disagree with a technical decision, how does that play out?" If the answer is "I don't usually disagree," that's not harmony. That's someone who learned speaking up costs more than staying quiet.

"If a friend asked whether they should join this team, what would you honestly tell them?" People rarely lie when it's framed as advice to someone they care about.

"How do you know when you've done good work here?" If they can't answer, your org hasn't made it clear.

You don't need ten questions. You need three honest ones and the discipline to stop talking after you ask them.

The engineers who answer carefully are often your best performers trying not to get fired for saying what's broken. The ones who say "everything's great" in week one say it again in their exit interview.

♻️ Repost if you've learned more from one honest answer than a dozen safe ones

➕ Follow me (Phillip R. Kennedy) for more on leading teams with better questions

He'd been the fastest developer on the team for nine years. Last quarter, a mid-level with half his experience outshipped him three to one.

She wasn't a better coder. She'd quietly changed what her job was.

Rachel started using AI agents the way a good manager uses a team: delegate predictable work, provide context, review output, redirect when something drifts. Agents handled integrations, test coverage, docs. She focused on architecture and judgment calls between what agents produced and what the system needed.

Still an IC on the org chart. Her daily work looked like management.

David coded line by line. Nine years of it. Genuinely good. He'd see no IDE on her screen and assume she was slacking.

Then sprint reviews told a different story.

Rachel shipped three features in a cycle where David closed four tickets. Not because she was smarter. Because she'd changed the ratio between thinking and typing.

His response is one I hear constantly: "That's not real engineering."

I get it. If you built craft through your hands for a decade, watching someone achieve more by orchestrating feels like a violation. Not just a career concern. An identity one.

But stripped of hype, here's what's happening.

The IC role is shifting from production to orchestration. From writing every line to directing, reviewing, and integrating work AI produces. The skills this demands aren't new. They're management skills. Providing context. Reviewing with judgment. Knowing when to intervene. Maintaining quality when production outpaces review.

Every engineer is becoming a manager. Not of people. Of systems that produce at a pace no human can.

The IC track isn't dying. It's evolving. More judgment. More context. Less typing. More thinking.

For engineers willing to make that shift, it's the best version of the job they've had.

♻️ Repost if your role is quietly shifting from building to orchestrating

➕ Follow me (Phillip R. Kennedy) for more on the real AI shift in technical work

She accepted an offer for 15% more. Her manager started a counteroffer. I told him to stop.

The money wasn't the problem. He just didn't know what the problem was.

Days before notice, her fix prevented a major outage. Week before, her refactoring cut response times in half. Her architecture decisions saved thousands in cloud costs monthly.

Her manager knew none of this. Not because he didn't care. Because he was a non-technical founder at a $12M company and nobody taught him what to look for.

He saw tickets closed. Features shipped. Through that lens, every engineer looked the same.

She didn't feel underpaid. She felt invisible.

This is the pattern I see most in growing companies. The founder is sharp. Competent in their domain. But they evaluate engineering like a restaurant kitchen: if food comes out, everything's fine.

The engineer preventing outages looks identical to one doing unremarkable work. Both close tickets. The difference is invisible unless you know what great engineering looks like.

That's not a character flaw. It's a knowledge gap. And it's expensive.

After she left, I told him: you don't need to understand code. You need three sentences.

"I heard your fix Tuesday prevented a customer issue. Tell me about it." Engineers know instantly if recognition is genuine. Specificity is the difference.

"What technical work happened this month I'd never see in a sprint review?" This teaches you what's invisible.

"What should I understand better about what engineering does?" Most leaders won't ask. Feels vulnerable. That's why it works.

The counteroffer would've cost $30K. She'd have stayed six months and left anyway. Her best work looked the same as average to the person signing her check.

Engineers don't leave for better offers. They leave when no one can tell the difference.

♻️ Repost if you've seen an engineer leave because leadership couldn't see it

➕ Follow me (Phillip R. Kennedy) for helping non-technical leaders keep great engineers

She stopped getting invited to strategy meetings in month four. By month eighteen, she'd stopped noticing.

That's the scary part.

Not the exclusion. The adaptation. Priya rebuilt their payment system from scratch. Designed architecture that scaled them from 200 to 2,000 concurrent users without adding. When their biggest client threatened to leave over reliability, her monitoring work saved the account.

The CEO texted the CTO about technical feasibility. Never Priya. The CFO questioned velocity at board meetings she wasn't in. Product roadmap happened Tuesdays. She found out Thursdays, after decisions were locked.

She wasn't failing. She was being compressed. Compression doesn't feel dramatic. You don't notice the ceiling dropping. You just start hunching.

By month twelve she'd stopped proposing improvements. By eighteen she was executing what others decided, calling it "being a team player," wondering why she was so tired.

I asked her when she'd last made a decision nobody above her rerouted. Too long before she answered.

Decades of this work. The pattern repeats. The CEO calls engineering "the IT group" at board meetings. Not just a wrong label. Labels shape budgets. Budgets shape headcount. Headcount shapes what Priya gets to build. When systems fail and the first question is "who did this" instead of "what happened," leaders absorb that. Stop taking risks. Stop volunteering hard truths. Shrink to fit.

She left. Smaller company. CEO with an engineering background. Six months later she told me: "I forgot what it felt like to have an idea and be allowed to finish the sentence."

She hadn't gotten smarter. She'd gotten room.

If something in your chest just tightened, pay attention to that. Not every struggle is a skills gap. Sometimes the ceiling is just low.

♻️ Repost if you've felt the difference between being grown and being compressed

➕ Follow me (Phillip R. Kennedy) for building environments where technical leaders thrive

They spent eight months building an AI recommendation engine. Beautiful machine learning. Garbage recommendations.

Their product catalog had 847 duplicate entries and descriptions from 2020.

The AI did exactly what it was designed to do. Found patterns and served them confidently. Customers got recommended discontinued products, duplicates of things in their cart, accessories for items no longer sold. Confident wrong answers at machine speed.

This company isn't unusual. They're the norm.

The pattern is becoming too common. The CEO hears AI is table stakes. The board wants a strategy. So leadership announces an initiative while their systems run on spreadsheets, manual uploads, and that one person who reconciles the data every Friday.

Customer records in seventeen tools. Support tickets referencing orders that don't exist in the main database. Three definitions of "active customer" depending on which dashboard you open.

Then they layer AI on top and wonder why it doesn't work.

AI doesn't fix broken systems. It scales them. Wrong answers with perfect grammar. Three versions of truth delivered faster than ever.

The most effective AI deployment I saw last year was boring. Nine months of cleanup before writing a single prompt. Data consolidated. Duplicates resolved. Systems connected. One source of truth.

No press release. When they turned on AI, it just worked. Not because the technology was special. Because it had something sane to work with.

Before you spend another dollar on AI: would a new employee be confused by your current systems? If yes, so will the AI. Just faster and more expensively.

The companies quietly winning aren't the ones with the biggest AI budgets. They're the ones who did the boring work first.

♻️ Repost if you've watched AI get layered on a foundation that couldn't support a spreadsheet

➕ Follow me (Phillip R. Kennedy) for technology decisions that actually work

He told the CEO he was 60% sure. The CEO said, "That's 20% more than I had when I started this company. Go."

Daniel had been circling a platform decision for three weeks. Two viable paths. Trade-offs he could model, risks he couldn't. The data said "maybe" in fourteen different ways.

He kept requesting more analysis. Another benchmark. One more comparison. His director finally said, "You're not gathering information. You're avoiding a decision."

She was right.

Daniel could architect systems most people couldn't diagram on a whiteboard. The problem was never capability.

He'd confused certainty with competence.

He believed good leaders decide because they know the answer. So when he didn't know, he assumed he wasn't ready. More data. More time. The team stalled.

The CEO's response broke something open. Every founder who's built something real knows certainty almost never arrives on time.

Daniel made the call Thursday. "Here's what we're doing, here's why, and here's what I'm not sure about. We'll learn the rest by building."

Six months later, two of his assumptions were wrong. The team had adapted. What he'd agonized over mattered less than the momentum of actually moving.

This pattern lives everywhere. The leader who won't commit until every variable is known. The founder polishing the deck instead of making the call. The executive requesting another quarter of data before approving a hire they know they need.

It looks like diligence. Past a certain point, it's avoidance in a professional costume.

Courage doesn't follow confidence. It's the other way around.

Daniel told me a year later: "I used to think my job was to have the answer. Now I think it's to make the call and help the team navigate what we find on the other side."

That's not a technology insight. That's a leadership one.

♻️ Repost if you've made the right call on incomplete data and didn't know it until later 

➕ Follow me (Phillip R. Kennedy) for more on leading through uncertainty

They hit every sprint target for eleven months. Green across every dashboard. The board loved them.

Their production system was rotting from the inside.
I got called after the third senior engineer left in six weeks. The CEO was baffled. "Velocity is up. Deployment frequency is the highest it's been. Why are they leaving?"

I spent a week with the team before opening a dashboard.

Engineers had learned to game every metric leadership tracked. Points inflated. Deployments split into smaller chunks. Tickets closed at "good enough."

The burndown charts were beautiful. The codebase was held together with workarounds nobody touched.

Nobody had raised it. The one engineer who tried, eight months earlier, got told metrics showed everything was fine. Last time anyone spoke up.

The moment I knew the team was in trouble wasn't in a report. It was in planning. A junior engineer pushed back on a timeline. Got two sentences in. The room went still. Not respect. Warning. She stopped. "Never mind, we can make it work."

On a healthy team, that sentence never gets cut short.

The signs that matter have nothing to do with velocity. When something breaks, does the team ask "what failed" or "who failed?" When someone says a deadline is unrealistic, does the room listen or reroute? Does the team celebrate three weeks of database work nobody outside engineering will notice?

These behaviors don't fit in Jira. They're the difference between a team that ships metrics and one that builds systems you can bet a company on.

His best engineers hadn't left for comp. They left because they'd been saying the system was fragile, leadership pointed at green dashboards, and they decided to let the next team deal with it.

Prevention never shows up on a dashboard. But it's the reason you still have a business.

♻️ Repost if you've seen the gap between what metrics show and what's really happening

➕ Follow me (Phillip R. Kennedy) for seeing what dashboards miss in engineering teams

I watched him delete a Slack message. He'd started typing a direct answer to an engineer's architecture question, stopped, and forwarded it to his direct report instead.

He'd been VP for eleven days.

James had been a director for three years. Engineers loved working for him. Answered questions directly. Showed up in code reviews to learn. Knew the last five production incidents by heart.

Eleven days in, something shifted. A quiet recalibration of who he thought he was supposed to be.

Stopped joining sprint demos. Replaced architecture chats with "strategy alignment" meetings. When engineers pinged him, he forwarded the message.

He wasn't arrogant. He was doing what he thought VPs do. Every VP he'd watched kept distance. Details were for directors.

The system was turning a connected leader into an abstraction.

I'd seen it dozens of times. The title lands and the operating system changes. Not because the person changed. Because the calendar fills differently. Information arrives filtered. You stop hearing what engineers think and start hearing what managers think engineers think.

Three months in, his team didn't recognize him. Engineers routed through his chief of staff. The architect who used to argue with him had stopped, because James was no longer in the room where those arguments happened.

I told him: "You used to spot the caching problem before anyone filed a ticket. Now you find out in a weekly summary. That gap is where your judgment lived."

He made a few changes. Kept one architecture session weekly. Not to decide. To listen. Stayed in sprint demos for his most critical product. When engineers pinged him, he answered directly.

Small things. But the team noticed immediately: proximity isn't beneath me.

The title doesn't have to change you. But it will, unless you choose which connections to protect.

♻️ Repost if you've watched a promotion quietly rewire someone

➕ Follow me (Phillip R. Kennedy) for leadership that stays connected to the work

The CTO told me he'd spent his weekend studying AI augmented development. His background was finance. His best engineers were leaving. He thought the two problems were connected.

They weren't.

Daniel had been CTO for eighteen months. Smart. Great with numbers, strategy, board communication. Zero engineering experience. He assumed credibility meant closing the gap. So he studied. Tutorials. Whitepapers. Architecture reviews full of detailed implementation questions.

His engineers didn't see a leader learning. They saw a bottleneck forming.

Every decision became a research project. Three-week sprints stretched to six because nothing moved until he felt informed enough to approve. He thought he was being thorough. His team experienced it as distrust.

The senior engineer who left first told me: "I don't need my CTO to understand AI development. I need him to trust that I do and make the call."

That's the gap. Not technical knowledge. Decision-making confidence. Daniel didn't need to understand how to setup OpenClaw. He needed to recognize his senior architect had been right about the last four calls and earned trust to make the fifth without a two-week wait.

The hardest part of leading technical teams without a technical background isn't the knowledge gap. It's saying "I don't fully understand this, I trust your judgment, here's my decision." That terrifies most non-technical leaders. It's also what stops your best people from updating their LinkedIn profiles.

We worked on this together. He stopped studying how to technically implement AI. Started making faster calls based on who recommended them and what they optimized for. Approval cycles shortened. His team stopped leaving.

He told me: "They didn't need a better engineer. They needed faster decisions."

His engineers could have told him that on day one.

♻️ Repost if you've learned that leading technical teams is about decisions, not expertise

➕ Follow me (Phillip R. Kennedy) for more on leading technical teams with confidence, not code

His hands were shaking over the keyboard. He'd deployed the change that took checkout offline. Everyone in the room knew it.

Revenue stopped. Tickets stacking. VP of Sales pinging me for an ETA I didn't have.

The room wanted someone to bark orders. Demand root cause. Point at the deployment log.

I sat down next to him. "How many customers are affected right now?"

Not "what happened." Not "whose change."

He stopped staring at the error logs. Pulled up monitoring. "About 1,200 in checkout. Another 300 getting timeouts on product pages."

"Good. Checkout first. Walk me through the rollback."

His hands stopped shaking by the third sentence.

A leader's emotional state during an incident becomes the team's operating environment. Instantly. Walk in radiating urgency and everyone matches it. They talk over each other, chase parallel theories, make decisions that feel productive and create more problems.

Walk in calm and something shifts. The engineer who caused the outage stops bracing for blame and starts working the problem.

The fix took ninety minutes. He found it himself. A config flag that behaved differently in production than staging. After systems were restored, I told the team to go home. Handled the sales update myself. Scheduled the postmortem for two days later, because running a blameless retro on no sleep is how you get a blame-filled one.

Two days later, he proposed the fix: automated config comparison between staging and production. Nobody asked him. He volunteered because the incident room had been safe enough that owning it didn't feel like a career risk.

A year later he led our incident response. Calm. Methodical. Sat next to the person panicking instead of standing over them.

He learned that from a Tuesday afternoon when his hands were shaking and nobody blamed him for it.

♻️ Repost if you've seen calm leadership change the outcome of a crisis

➕ Follow me (Phillip R. Kennedy) for more on leading technical teams through hard moments

We've all made the "perfect résumé" hire. Strong credentials. Nailed the technical interview. Three months in, you realize they can solve any problem except the ones that actually matter.

I've hired hundreds of people over thirty years. The pattern that predicts success has almost nothing to do with algorithms or credentials.

It's curiosity. How someone behaves when they hit a problem they don't know how to solve.

One of my best hires had two years of experience and a community college degree. Struggled in the technical round. But when conversation shifted to a real problem we were facing, he asked diagnostic questions that showed he'd operated systems under real pressure. Not textbook answers. Thinking from the weeds.

A year later, three teams called him first when something broke. Not the fastest coder. The one people trusted to think before acting.

What I've learned about what actually predicts success:

Give candidates a real problem, not a puzzle. Walk them through a challenge your team faces. Twenty minutes of real conversation beats an hour of whiteboard performance.

Watch what happens when they don't know. The best say "I haven't seen this, but here's how I'd start." People who bluff in interviews bluff on your team.

Listen to what they ask about. The system, the users, the team? Or just the stack, the title, the comp?

Look for ownership instinct. Ask about a project that went sideways. People worth hiring talk about what they learned. Not who was at fault.

Create unstructured time. Thirty open minutes surface what no template will.

You can teach your tech stack in months. You can't teach someone to care about the problem behind the ticket.

The résumé says where someone's been. The conversation tells you who they are. Most hiring processes only measure the first.

♻️ Repost if your best hire looked nothing like you expected on paper

➕ Follow me (Phillip R. Kennedy) for more on building teams that scale on trust

Career advice nobody's giving: Quit. Stack Mac Minis. Subscribe to every AI model and claw bot. Emerge in 90 days as something the market doesn't have a job title for yet.

If you're an agency owner or B2B founder who knows X and LinkedIn could be your #1 client source..

But it's just another platform to manage, another audience to build, and you simply don't have the time.

When did you last buy a high-ticket service from someone with a weak brand? 

Your prospects are doing the same thing. If they can't find you, they're choosing someone who looks like the authority. They're not better than you. They're better known.

Here's how I can help you become the go-to authority:

I'll plug your brain into my system and run your entire X & LinkedIn presence for you. My clients typically close 5-10 new clients in 90 days while spending less than 1-2 hours per month.

Here's the trap most people fall into:

They post inauthentic content that blends into the noise. They have dead audiences, so the algorithm never shows their posts to new people. And they DM blast hard pitches that disgust prospects.

The result? No know-like-trust factor = no sales.

I've worked with 30+ experts and B2B founders, including Client Ascension, Whop, Shown Media, and Hire Spartan. My content has generated 16M+ views and 6 figures in revenue.

Unlike most ghostwriters, I walk the talk. I've personally generated 7.5M views and signed 30+ clients through X & LinkedIn, building one of the most engaged audiences in my space—outperforming accounts 5-10x my size. 

Within 39 days of starting LinkedIn, I was accused of using engagement pods. I wasn't. I just knew what worked.

Here's my system:

→ Monthly interviews to extract your insights and expertise
→ Content written in YOUR voice that attracts your ideal buyers
→ Community building with prospects who engage and amplify your reach
→ Personalized outreach to qualified leads (we hand them off warm—you just close)

Real results:

• Christian: $4K client closed in 10 days
• Huseyin: 1K to 5K followers, 15 new clients
• Filip: 90 to 2K followers on X, 10 clients
• Michael: $2.5K deal closed 4 days after starting

Why we're different:

We use your authenticity to stand out. While others chase vanity metrics, we build communities of your ideal buyers. 

We guarantee results: 5-10 new clients in 90 days, or you don't pay. This isn't theory—I've built this exact system for myself and proven it works.

Your personal brand should work 24/7 while you focus on delivery and scaling.

Want to position yourself as the go-to authority and sign clients consistently?

Book a free 20-minute strategy call. I'll audit your X & LinkedIn presence and create a custom roadmap.

https://go.leveragedcreator.io/

Onat Aksaray

My first $250 client took me hours to close.

My $4k/month client?

Said "let's start" 1 second after hearing the price.

Here's what I learned about lead quality:

My $250 client process:
- 1 hour sales call
- Multiple follow-up calls 
- Endless back-and-forth DMs
- "It's expensive" objections

My $4k/month client process:
- One sales call
- Heard the price: "Let's start"
- No objections
- Ready to pay many times more

The difference wasn't my sales skills.

It wasn't a fancy funnel.

It was lead quality + trust.

My $250 client was price shopping. 
My $4k client was solution shopping.

He didn't need convincing. He needed confirmation.

What's even better?

I used this same outreach strategy to close 2 high quality clients last week.

While others chase cold prospects who say "I'll think about it,"

I create conditions where excited prospects reach out ready to pay premium prices.

Stop wasting time on prospects who see you as expensive.

Start attracting clients who see you as essential.

The lesson? Lead quality beats lead quantity every time.

Build trust first. (With quality leads)

Sales will follow.

Engineering profitable X & LI brands for B2B founders | My content generated 16M+ views & 6 figures in sales. 30+ clients served. | Book a free content audit below.

Gurus tell you to comment under big accounts to grow.

Here's why that's terrible advice:

They tell you to comment under accounts getting millions of views to "steal their views" and drive traffic to your profile.

That's so wrong.

(and I think they mainly say this so you comment under THEIR posts lol)

Here's what actually happens when you chase big accounts:

• They won't care about your comment
• They won't even know you exist 
• They won't return the favor
• No one reads those comments except the creator
• If they get 100s of comments, yours gets buried

You're not "stealing views." You're wasting time.

I do the opposite.

I comment and DM smaller accounts around my level.

Why? Because they actually care about you.

This is what I call building a "Gravity Network."

You attract similar people around you like gravity and support each other mutually.

The results speak for themselves:

3 months ago: 
176 LinkedIn followers, 0 posts

Today:
2700+ followers and 200k+ impressions generated on LinkedIn

That's also how I generated 16M views without paying for ads or being cringe on X.

Now I'm applying the same strategy on LinkedIn.

And 7-8 people have already reached out asking for LinkedIn advice - people who've been posting for months.

Here's the truth most gurus won't tell you:

If your audience doesn't engage, the algorithm thinks your content is bad and stops showing it to new people.

That's why I prioritize making friends over chasing influencers.

You don't need to go viral.
You don't need clickbait hooks.
You need consistent engagement from people who actually care.

Make friends with creators at your level or slightly below.

Build your community first.

You won't worry about visibility again.

I removed all my friends on LinkedIn before posting.

Here's why:

I wanted a complete digital detox from judgment.

That's something I learned from Lara Acosta.

She calls it "digital detox".

No, it's not about deleting Instagram and Tiktok.

Before my first post I had around 450 connections.

I spent 3 days removing all my friends.

After 5+ hours spent, I only had 176 connections.

The only people that were left were the people that would be interested in what I talk about.

No one else.

You may think I went backwards and hurt my progress..

But you are wrong..

See, most people are paralyzed by one thing when creating content:

"What will my colleagues say?"
"What will my friends think?"
"What if my boss sees this?"

So play it safe. 
Water down their message. 
Post generic advice that sounds like everyone else.

The result? 

Zero engagement. 
Zero authentic connection.

I've only been posting here for 4 months.. 

But I get more engagement than people who've been posting for months.

Why?

Because I post without the fear filter.

When you remove the audience that knows you personally, you can finally be yourself professionally.

You stop trying to maintain an image and start building a brand.

You share real struggles instead of fake wins.
You give honest opinions instead of safe takes.
You tell your actual story instead of a polished version.

That' how I built a profitable on X in the first place.

I started from zero and posted without fear of judgement.

Not by playing it safe, but by being authentically me.

The people who matter will find you.
The people who judge you weren't your customers anyway.

Sometimes the best way to grow is to subtract before you add.

Your authentic voice is your competitive advantage.

Stop hiding it.

My first client was an accident.

(It changed how I approach sales)

2 years ago, I was just another struggling entrepreneur posting on online.

Failed many businesses.

But I kept showing up anyway.

One day, I commented on someone's post. 

Not to sell anything. 

Just to add value to the conversation.

They checked my profile.

We started chatting.

No cold DMs.
No fancy funnels.
No pushy sales scripts.

Just two humans talking about their challenges.

Then something magical happened.. 

He wanted more help.

That "accident" became my first paying client.

Here's what I learned:

People don't buy from brands. They buy from humans.

The moment I stopped trying to "sell" and started genuinely connecting, everything changed.

Now my approach is simple:

1. Show up consistently with valuable content
2. Engage authentically in conversations 
3. Let relationships develop naturally
4. Help first, sell second

This strategy has helped me serve 30+ clients.

My clients don't just hire me for my expertise. 

They hire me because we've built genuine trust through real conversations.

The best leads aren't found.

They're created through authentic connections.

Your next client might be one genuine comment away.

I told my family I'm searching for jobs.

While I was silently building online:

The pressure was there. 

Family dinners became interrogations about my "job search progress." 

Friends were sending me LinkedIn job postings. 

My family was skeptical about this whole "online business" thing.

But here's what they didn't know:

I was working everyday building my personal brand on X.

Writing content, engaging with my community, and developing my coaching offer.

Learning everything I could about personal branding and marketing.

The hardest part wasn't the work itself.

It was keeping quiet about the small wins:

Landing my first paying client
My first viral post hitting 100k views
Building genuine relationships with other creators

While everyone saw someone "struggling to find work," I was actually building my freedom.

Fast forward to today:

I'm working with 7-8 figure business owners.

They wanted me to write one post.

Why did they choose me over everyone else?

"Other posts sounded the same. Yours was different."

I sounded like me.

The same family members who were worried about my future? 

Now, they are proud of how far I've come.

Sometimes you have to disappoint people temporarily to create the life that will make them proud permanently.

Stop trying to fit in. 

Your weirdness might just land you your biggest client.

Trust your vision, even when others can't see it yet.

I started with 176 random connections & 0 posts.

Now, my content outperforms people 5x my size.

What changed?

Here's what I did differently:

Instead of cold pitching → I built genuine relationships

Every comment I left was to add value, not to sell.
Every DM I sent was to connect, not to convert.
Every post I shared was to help, not to promote.

The result?

In just 2 weeks:

My posts get 60-120+ likes.
I've connected with incredible entrepreneurs.
People are reaching out to ME instead of the other way around.

The secret isn't complicated:

Create content that builds relationships, not just followers.

Most people on LinkedIn are doing relationship building backwards.

They think: 

Post → Get followers → Build relationships

But it actually works like this: 

Build relationships → Create valuable content → Attract the right people

When you focus on genuine connection first, everything else follows.

My simple framework:

Share your real journey (the struggles, not just the wins)
Engage authentically with others' content
Start conversations, don't just broadcast
Help before you sell

This approach isn't just working on LinkedIn.

It's the same strategy I used to build a multi 5-figure business on X with just 5k followers.

Small audience, big relationships = real results.

Quality connections will always beat quantity metrics.

The bottom line:
Stop chasing vanity metrics.
Start building real relationships.

The engagement will follow naturally.

I don't comment 300x a day.
I don't send 50 DMs a day.
I don't post everyday.

Instead?

I focus on helping my clients.

And I had clients stay 8+ months.

That's my secret.

Here's what most brands get wrong:

They think success comes from volume. 

More comments, more DMs, more posts.

But they're playing the wrong game.

While everyone else is chasing vanity metrics, I'm building something that actually matters: client results.

The truth about sustainable business growth:
→ Quality beats quantity every time
→ Client retention is more valuable than client acquisition
→ One happy long-term client is worth 10 short-term ones

My approach is simple:

I show up consistently (not obsessively). I create content that serves my audience. I focus on delivering real value to the people who trust me with their business.

The result? 

Clients who don't just buy once and leave. 
They stay, they refer others, and they become genuine advocates for my work.

In a world obsessed with growth hacks and viral strategies, sometimes the best approach is the most obvious one:

Do great work. 
Keep your promises. 
Take care of your people.

Everything else is just noise.

"Why does my content feel boring"

Because you're hiding.

Your quirks? 
Your opinions? 
Your personality?

That's what makes you interesting.

I learned this the hard way.

For months, I tried to sound like every other "professional" creator:

Generic business advice
Corporate-speak everywhere 
Zero personality showing through

Result? My posts flopped consistently.

Then I made a decision that changed everything.

I started sharing my real story:

How I failed 5+ businesses before this one worked. 
How English is my third language but I still create content in it. 
How I take hot showers and wake up at 9am.

The difference was immediate.

People started connecting with the human behind the brand, not just another faceless expert.

Here's what I realized about building an authentic personal brand:

Your "flaws" are actually your differentiators. Everyone has results and credentials. Not everyone has your unique perspective and story.

Being relatable beats being perfect. 

My clients often tell me they chose me because "we're the same age" or "you look like my younger self" - not just because of my results.

Memorable trumps professional every time. You can be the most qualified person in the room, but if you're forgettable, you won't get chosen.

Stop hiding behind the "professional" mask.

Your quirks, your journey, your personality - that's your competitive advantage.

The market is oversaturated with experts.

But there's only one you.

Focus on being memorable.

Posts flopped? 
I showed up everyday.

Posts went viral?
I showed up everyday.

Leads ghosted me?
I showed up everyday.

Closed 4 figure clients?
I showed up everyday.

Traveling?
I showed up everyday.

Here's the truth most creators won't tell you:

Consistency beats talent every single time.

3 years ago, I was a quiet engineer who failed 5+ businesses. Lost the little money I had. Everyone doubted me - family, friends, girlfriend.

It was the hardest time of my life.

But I made one decision that changed everything:

Show up no matter what.

• When my posts got 50 views instead of 1000+
• When nothing seemed to work
• When I felt like giving up
• When leads ghosted me
• When I was traveling

I showed up anyway.

The result?

I made multiple 5 figures by posting tweets.

All from a small personal brand.

Most people think they need:
- 8 hours a day to dedicate
- 100k followers to start
- To be the best expert in their niche
- Perfect content from day one

Wrong.

You just need to show up.

When you commit to consistency, everything else becomes easier.

The compound effect of showing up is unstoppable.

Start today. 
Show up tomorrow. 
Repeat it for 365 days.

Your future self will thank you.

I got C- from Academic Writing in college.

Now I write for 8 figure founders.

Here's the irony:

That class taught me to add fluff words to hit word counts.

"Use more sophisticated vocabulary."
"Expand your sentences for clarity." 
"Meet the minimum page requirement."

All terrible advice for online writing.

Fast forward to today:

• 16M+ total views online
• 10k+ total engaged audience
• Clients pay $1.5-$4k to write for them

How?

I unlearned everything college taught me about writing.

Instead of writing to impress professors, I write to connect with people.

Instead of using big words, I use simple ones.
Instead of long paragraphs, I use short sentences.
Instead of fluff, I get straight to the point.

The writing that got me a C- in college?
It would get me fired as a content creator.

The writing that makes me money online?
My professor would have hated it.

School teaches you to write for academics.
The internet teaches you to write for humans.

Less is more when writing online.

Sometimes you have forget what you are taught.

And look at what the market rewards.

What was your worst subject in college?

I used to earn $750/mo in my first 9-5.

I was depressed.

But now?

• I love my work
• I wake up when I want 
• I get paid to do what I love

Because I made a decision.

I stopped waiting and took action.

Here's what changed everything:

I was a quiet, shy engineer working at a tech startup. 

Despite graduating from university and landing what seemed like a "good job," I felt completely stuck.

The turning point? 

I quit that job everyone thought I was crazy to leave.

But instead of giving up, I got strategic.

I started working as an appointment setter for a successful online business. 

Set 7 figures worth of appointments in the pipeline. 

This gave me the confidence and skills I needed.

Then I discovered the power of personal branding on X.

It felt like play, not work. 

But I still struggled for months, spinning my wheels while everyone around me doubted the path I was on.

The breakthrough came when I found my tribe - like-minded people on the same journey. Got mentors. Built authentic relationships instead of chasing influencers who ignored me.

The biggest lesson? Stand out with authenticity.

When you build authority through authentic content, quality prospects reach out to YOU instead of you chasing them.

Stop waiting for the "perfect moment" to start building your brand.

Now I hit $15k/mo last month and feel like I'm just starting out.

The best time was yesterday. The second best time is now.

Your expertise deserves to be seen. 

Your story matters. 

Your audience is waiting.

Take action today.

2 years ago I said "f*ck it" & went all in on building online.

It's been the best decision I've ever made..

A few months before I just left my "stable" job at a tech startup, I started questioning everything.

I had worked so hard to get that tech job at a US startup backed by big VCs.

I have nothing against that job.

But the truth was: I wanted to something else.

At least I wanted to try my luck at something that I really found interesting.

I told my family that I was searching for other jobs but I was actually looking for business ideas.

So while I was questioning what I really wanted from my life, I discovered Dan Koe.. 

And this whole "personal branding" thing on X.

At that point I had 0 social media experience but I thought I could do it.

Quitting wasn't simple though. My brain kept saying:

• What if I fail completely?
• Can I actually make money from tweets?
• My engineering background won't help with this
• Everyone will think I've lost my mind

Turns out these thoughts were complete nonsense.

They almost stopped me from pursuing my actual dreams.

Where I am now:

I served 30 clients served through my brand.

Considering a similar leap?

My perspective:

Corporate jobs offer fake security.
Taking zero risks guarantees zero rewards.
Perfect timing is a myth that keeps you stuck.

Fear is expensive. Regret costs more.

I started to enjoy looking stupid.

My best business decision ever:

My first post? Stupid.
My first offer? Stupid.
My first cold DM? Stupid.

But here's what happened next..

Every day I sucked a little less.

While others waited for perfection, I was building.

Here's the truth most entrepreneurs won't tell you:

When they started out, they looked stupid, too.

I used to be that engineer who overthought everything:
- The perfect bio
- The perfect business plan
- The perfect content strategy 

I was always entrepreneurial but mostly inside.

Most of my thought didn't make it to the outer world.

I waited 10 years to make my first post online.

Then I realized something..

Nobody remembers your failures.

They only remember your results.

Last 10 days? 

I closed 3 clients worth 1.5k - 4k per month each.

All because I got comfortable being uncomfortable.

The goal isn't to avoid looking stupid.

The goal is to look back at your old content and cringe.

That cringe? That's called growth.

Your willingness to put yourself out there.

That's the only way you get "lucky".

My first month on LinkedIn:

9 AM: Write a post
11 AM: Check analytics
1 PM: Check analytics
3 PM: Check analytics
5 PM: Check analytics
7 PM: Feel defeated

Sound familiar?

I was trapped in the analytics addiction loop.

Every notification became a dopamine hit. Every view count became validation. Every like became proof of my worth.

But here's what happened..

When I obsessed over numbers, the progress staagnated.

I started writing for the algorithm instead of for people. 

My engagement was stuck. My growth was stagnant. And worst of all? I wasn't enjoying posting.

Then I made a decision that changed everything:

I check analytics a few times a week.

Now?

I write when inspired.
Help when needed.
Post when ready.

The irony? The moment I stopped obsessing over numbers, they started growing.

Why does this work?

When you're not distracted by vanity metrics, you focus on what actually matters:

- Creating valuable content
- Building genuine relationships
- Helping your audience solve real problems

Your energy shifts from metric-chasing to value-creation.

And guess what people respond to? 

Value. Not your view count.

I made the same mistake when I first started on X but it took me 6 months to fix it on X.

After I fix it? I built my following to 57+ and generated millions of views.

Now I'm building my LinkedIn presence on public to replicate the same success. 

This lesson applies everywhere:

Focus on the input, not the output.

Are you checking your analytics too often? 

Time to break free from the addiction.

The numbers will follow when you serve your audience authentically.

I'm not special. 
I'm not a genius. 
I'm not an extrovert.

My only difference?

I just don't give up.

What if I fail?

I'd still keep going.

Because failure is the best teacher.

I graduated as an engineer.
Worked at a VC-backed tech startup.
Quit the job I worked so hard to get.

Then I failed. Hard.

• Started 5+ businesses that crashed
• Lost the little money I had 
• Family worried I was making a mistake
• Friends saw me struggling while they succeeded

Everyone doubted me.

But here's what I learned:

Success isn't about being the smartest person in the room.

It's not about having perfect genetics or social skills.

It's about showing up when you don't feel like it.

It's about trying again when everyone tells you to quit.

Today?

I work with clients that I enjoy.
I impacted 1000s of people.
I have location freedom.

The difference between winners and quitters isn't talent.

It's persistence.

While others gave up after their first failure, I kept going.

While others listened to the doubters, I trusted my vision.

Your breakthrough is often one failure away from happening.

Don't let temporary setbacks become permanent defeats.

Keep going.

My morning routine is terrible.

But it made me more than my old salary.

No cold showers.
No 5 AM wake ups.
No meditation apps.

But I did one thing right:

I built systems that work for me.

Now I make more than my old 9-5 salary.

While being myself.

Here's what I learned after quitting my tech job and building $10k/mo online business:

Your routine doesn't need to look like everyone else's.

I used to think I needed to follow the "perfect" morning routine to succeed online. 

Wake up at 5 AM, cold shower, journal for 30 minutes, meditate.

I tried it all. It felt forced and unnatural.

Then I realized something important...

Success isn't about copying someone else's system.

It's about building one that fits YOUR life.

My actual morning routine?
- Wake up around 10-11 AM
- Coffee first (always)
- Check messages from my community
- Review my content calendar
- Start working on what matters most

Is it Instagram-worthy? No.

Does it generate results? Absolutely.

• Hit 10k+ total followers
• Generated 16M+ views
• Helped 30+ clients grow their brands

The productivity gurus won't tell you this:

You don't get rewarded for having the perfect routine.

You get rewarded for doing the work consistently.

Some of my best content ideas come at 11 PM.

Some of my biggest client wins happened on lazy Sunday mornings.

The real secret?

Find systems that you can stick to long-term, not ones that look good on social media.

Your energy is finite. Don't waste it fighting against your natural rhythms.

Instead, work with them.

Forget the rules.

Your business should fuel your life, not destroy it.

I went viral yesterday: 19k+ views, 500+ likes.

But what's even better?

I generated 10M views for myself online and I hardly go viral.

You don't need to rely on going viral when you build a community.

This wasn't on LinkedIn tough.

It was on X.

I've been on LinkedIn for the last 6 months and I can say that it's very similar to X.

People are already asking me how I gained traction so fast in a few months.

I started 4 months ago with 176 random connections and 0 posts.

Most of things are directly transferrable with a little bit of tweaks.

But I think X has a better organic content algorithm.

What I'll say here will work for both X and LinkedIn.

Most brands think going viral is luck.

It's not.

I've cracked the code on X's organic algorithm, and it's rewarding brands who understand these 3 things:

1. Treat each post as a funnel
Start with broad appeal to attract new audiences, then funnel down to your specific expertise. Most brands start too niche and lose 90% of potential viewers.

2. Build your gravity network
Stop chasing big accounts who ignore you. I engage with smaller brands at my level who actually reciprocate and amplify my content.

3. Save and iterate on what works
When a post performs well, I create 5 versions of that idea and post them weekly. One viral post becomes a content strategy.

The algorithm isn't broken.

Most brands are just creating content that doesn't build relationships with people.

Posting technical stuff without emotion.
Trying to sound like everyone else.
Not being vulnerable or relatable.

While others chase influencers who ignore them, I focus on building my gravity network with brands at my level.

The result? 

More organic reach.
Followers who actually engage.
And posts that turn into paying clients.

Don't blame the algorithm.

Creating content that builds authority and connection.

That's how you turn my life into viral content.

taplio

The Battle

Phillip R. Kennedy

Onat Aksaray

Followers

Posts

Engagements

Likes

Performance ScorePhillip R. Kennedy's LinkedIn Performance

Performance ScoreOnat Aksaray's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Phillip R. Kennedy

Onat Aksaray

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Phillip R. Kennedy's LinkedIn Performance

Performance ScoreOnat Aksaray's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScorePhillip R. Kennedy's LinkedIn Performance