MetaCTO

Mobile app design and development that helps business owners create new revenue streams, increase customer lifetime value, and improve profit margins.

Partner

olive

Head of Engineering

Round

Round is a curated community of technology executives and senior leaders who support, grow, mentor, and learn from each other. The Round experience supports leaders who are at the forefront of technology, working on products and services that have an outsized impact on the world.

Founding Member

Power Digital Marketing

Team and product leadership for the Nova platform at Power Digital Marketing. The machine learning platform that can analyze any business’s growth opportunities, build a marketing strategy to execute on them, and track progress across 13+ channels in custom-tailored dashboards.

VP Engineering & Product

KlientBoost

Founded, launched and sold a marketing tech SaaS product.

- Grew team of 6 engineers plus product design and support staff
- Managed feature roadmap, technical architecture, development, delivery, and support
- Produced 50% trial-to-paid customer conversions
- Created education path for junior engineers
- Managed agile process of reviews, retros, standup, backlog

The flagship product for Kite Software integrated with Google Ads API to analyze accounts with custom algorithms and generate ROI focused recommendations. Scaled to process millions of records at a time with AWS serverless and queue services. Built with TypeScript, Node.js, Express, Python, Serverless, React, Redux, CircleCI, Docker, Gatsby, GraphQL.

VP Engineering, Kite Software

Maverick

Lead server side API development and web application team to support iOS startup venture creating a new social community for empowering young women. genmaverick.com

Develop microservices with NodeJS and MongoDB.  React and redux front end development.  Machine learning for moderation and transcriptions.  Rapid feature development including comments service, trending algorithms, and gamification progression engine.  Support PHP Zend MySQL API framework.  Mentor and train team members.  Manage technical contractors and support the agile development process.

Software Engineering Manager

JNR Incorporated

- Designed and developed a Node.js and MongoDB microservice-based API with a custom Express Gateway on an AWS Lambda-hosted serverless environment (api.paymentrise.com).
- Built a React and Redux front-end web application for customers to redeem prepaid reward cards with unique offer codes for BoostMobile clients.
- Led the technical team for new product development, defined software engineering processes, and implemented Agile Scrum methodologies.
- Created a custom Python script for serverless S3 deployment integrated with GitLab CI/CD.
- Introduced Git, Continuous Integration (CI), and Agile project methodologies to the team.
- Led the migration of a data center to an AWS cloud-hosted environment.
- Developed and supported large-scale Prepaid Card Industry applications for incentive programs, card activation, and card ordering.
- Built a REST API to securely interface new applications with legacy cardholder data systems, ensuring PCI DSS compliance at all levels.

Senior Software Architect, Lead

Blink Development, Inc.

Founded Blink Development with one partner and grew to a peak staff over 10 employees servicing website development and marketing.  Launched and serviced over 40 projects in 5 years, generating over $1.5M annual gross revenue.  Served as lead developer on all major projects.

Founder & Lead Developer

Fletcher Jones Motorcars

Started as a PC installation technician in 1999.  Advanced through many positions over 11 years with responsibilities including database administration, web development, help desk, project management, vendor management, and ultimately data warehousing and BI analysis with C#, .NET MVC, SharePoint, MSSQL Server, and SSRS.

Business Information Analyst, Developer, System Admin

At MetaCTO, we build custom mobile apps that help businesses grow new revenue streams, create online communities, increasing customer LTV with digital products, and make client communication more personal.

Christopher Fitkin

Young software devs are in BIG trouble.

Yes, it’s AI-related. No, it’s not what you think…

AI is not just taking your job…. AI is taking your skill.

Back in the day, if I got stuck, I’d call a friend or watch some YouTube videos - building, breaking, fixing, understanding why. I wrestled with the code until it finally clicked. But those days are gone.

Less YouTube… more vibe coding with AI. Letting Cursor or ChatGPT handle the hard parts. Then… when things aren’t working, “It’s this stupid prompt!”

The problem isn’t AI writing mediocre code.
It’s that too many new devs are letting it ‘think’ for them.

That’s dangerous!

Not just for devs, but for the companies that will hire them. If this trend continues, it’ll become harder and harder to find experienced devs - not to mention… expensive!

If AI writes all your early code, you never learn why things work. And when something breaks (and it always does), you’re lost.

So if you’re learning to code… sure, use AI.

But don’t forget what actually makes you valuable… asking questions, getting explanations, exploring ideas, breaking things, fixing them.

Write code yourself.

AI won’t make coding obsolete.

Because coding isn’t the hard part. Thinking is.

Coding is just putting decisions into a machine. The real work happens before a single line of code is written:

→ Understanding the problem
→ Resolving ambiguity
→ Designing systems
→ Building something that actually works in the real world for real people

The engineering part.
Coding is the boring/easy part.
(or it should be, or you’ve already made a big mistake)

AI can clear away the boilerplate and speed up execution, sure. But it can’t tell you what to build, why it matters, or how it should behave under pressure.

That’s the hard part. That’s the human part. No tool for that yet, unfortunately.

That’s why great engineers will always matter… no matter how good the tools get.

My reflections as a seasoned dev.

How things have changed. And how nothing has changed.

When I started coding 20 years ago, I thought experience was about knowing the latest tech stack and knowing how to speak to stakeholders. But I’m wiser now.

Now I know it’s about pattern recognition.

You see enough product launches, tech fads, and “revolutions,” and you realize - most of it’s just a remix of the same few lessons.

Back then it was cloud computing. Then mobile. Then blockchain. Now it’s AI.

Every cycle starts the same way… big promises, endless hype, and a bunch of companies racing to “adopt” it before they even know why.

But the people who kept their heads down, focused on fundamentals, and used the new tools responsibly end up miles ahead.

That’s what I’ve learned as a dev, a CTO, and now as a founder.

The technology always changes.
The patterns never do.

You build. You test. You fail. You learn. Then you do it again.

AI is just the newest tool in the box. Powerful? Absolutely. Transformative? Potentially. But like every tool before it… it’s only as useful as the people using it.

And that’s what I love most about this work.

The technology evolves every year, but the craft of building new things is timeless. How cool is that?

A software dev agency can be EXPENSIVE.

Relying on vibe-coding can be CATASTROPHIC.

I’m seeing more and more founders come to me with apps that were “built with AI.”

They say: 
“Faster, cheaper, modern”

Reality says: 
“Chris, you’re about to spend 2+ weeks cleaning up this mess I made in 2 hours.”

Because 9 times out of 10, the code is slow, not secure, and stitched together with ZERO understanding of architecture. Functions deleted. Logic duplicated. API calls written by AI that don’t actually work in production.

They thought they saved money by going cheap.

But by the time I’m brought in, they’ve already spent 3x fixing what should have been done right the first time.

This is the hidden cost of “vibe-coding”… when developers (or agencies) lean on AI to “move fast,” but skip all the fundamentals: planning, testing, structure, and review.

AI can: scaffold + boilerplate.
AI can NOT: design a system, handle edge cases, think through the user experience.

If you’re hiring a dev team right now, make sure they:

a) Can explain why they’re using AI, not just that they are
b) Have a review process that catches AI mistakes early
c) Know how to architect clean, maintainable code

It’s cheaper - and far less painful - to get it built right the first time than to pay someone like me to untangle it later.

Hire builders > vibe-coders

A concerned friend asked me if he should worry about the AWS outage. My answer: "Nope! If AWS goes down, so does half the internet. Your customers will understand.”

Even the biggest players out there aren’t fully “multi-cloud.”

HubSpot and Jira could spend millions to make their systems redundant across AWS, Google Cloud, and Azure… but they don’t.

Why? Because it’s:

a) extremely expensive
b) extremely complicated
c) extremely unnecessary

99.9% of the time, AWS works flawlessly.
And when it doesn’t… they recover fast.
Simple as that.

“Multi-cloud” just doubles your complexity. You’re now maintaining 2 versions of your app on 2 platforms that don’t talk to each other. That means 2x the bugs, 2x the monitoring, and 2x the headaches…

All to protect against something that happens maybe once every few years.

If you’re a startup or SMB, my advice is to prioritize recovery, not invincibility.

You’ll make far more progress by building systems that bounce back quickly when things break instead of trying to prevent every possible failure forever.

So no, you don’t need to panic about AWS. 😉

Indeed is stopping senior devs mentoring junior devs.

Seems pretty shortsighted to me.

When I was starting out, I learned almost everything that mattered from senior devs who took the time to explain the “why” not just the “how”. These conversations made me think differently about architecture, tradeoffs, and people.

Mentorship shaped my entire career and I know a lot of devs who’d say the same.

So when I see companies like Indeed stepping away from mentorship in favor of AI “efficiency”… 
I understand (they think it sounds smart & boards love it). But it’s premature. And honestly, a bit shortsighted.

And it’s not just mentorship. Indeed hasn’t hired juniors or interns in years.

These points kept coming to my mind:

a) How will they keep up with inevitable amount of mistakes AI will cause
b) They’re losing future leaders (but shareholders need “NOW”)
c) Culture erodes fast (everyone under ‘senior’ panics & looks for other opportunities just in case)

Curious to hear everyone else’s thoughts though.

Businesses… this is a warning:

Don’t “use AI” for the sake of “using AI”.

Lately, I’m seeing articles of companies tracking how much their engineers use AI.

How silly!

I’m not a fan of all this “adopt AI or get fired” talk in the tech industry. If you’re forcing your team to “use AI more” just to check a box… you’ve missed the point of AI.

Good engineers use the right tool for the job - not whatever’s trending on LinkedIn. When you make AI usage a performance metric, you stop incentivizing results and start incentivizing “busy work”.

Think about it from a dev’s perspective -

If you’re going to pay them to use AI… you’ll get diagrams no one asked for, scripts no one runs, and dashboards that look cool but do nothing.

And for what?

Engineers are your most valuable asset. Not some AI tool you started to use in 2024 because every post on LinkedIn tells you to “leverage AI”.

Engineers are the reason any of this tech works in the first place!

So yes, AI can make good engineers faster.
But no, it can’t make bad incentives smarter.

I’ve been building things my whole life.

Age 5: messing around in MS-DOS and BASIC.

Age 16:
- got paid for my first “professional” project - a car auction site - in the form of a black 1990 Jeep Cherokee (still one of my favorite paychecks).

Age 18:
- went to college thinking I’d be a lawyer. Majored in Political Science & Italian. But the whole time, I was secretly doing my roommates’ CS homework because I just enjoyed coding.

After school, I skipped law school & took a job as a business data analyst.

Age 22:
- quit and started my first web dev agency. That lasted five years… then collapsed.

Age 27:
- spent the next decade in-house - startups, MarTech, AdTech, big engineering orgs. Built massive teams. Learned P&L, delivery, sales motions, investor pressure, and how thousand-person agencies really operate.

I think it was at this time that I realized something important: I’m a builder. First software. Then teams. Now companies.

2024:
- my now-business partner, Garrett, called me and said: “Hey, I’m starting an agency. Want to join me?”

I quit the next day.

Year 1 of MetaCTO:
- scrappy. Just a small team building great products, relying on our network, getting stuck in.

Year 2 of MetaCTO: 
- we went all-in on growth: SEO, PPC, partnerships. Grew ~300% YoY vs Year 1.

We started working with incredible people/companies:

• Jamie – Head of Engineering 
• Kristen – Head of Revenue 
• Closed official partnerships with RevenueCat, and building motions with AppsFlyer + CleverTap

We also hit major milestones: From near-zero organic traffic → 1,600 monthly visitors + 84 inbound leads last month.

We’re building MetaCTO into a $50M+ product & engineering partner.

So… why do I do this?

1. I love building things
- mobile app MVPs, AI features, even entire engineering org - creating gives me life.

2. I love helping others succeed
- I spent years building software for startups. I know exactly what founders go through: pressure, confusion, tradeoffs.

3. I want to build the company I wish I’d had as a partner
- a place where builders get to build, clients get clarity instead of bureaucracy, value gets created & not extracted

If you read this far - thanks.

This is the stuff I never shared, but probably should have years ago.

If you’re building a product and need help with strategy, AI features, or mobile execution… my DMs are open.

Bureaucracy kills creativity.

Daily standups, PR reviews, design reviews, stakeholder reviews of the design reviews…

You could spend a whole week talking about building… instead of actually building. That’s one of the biggest reasons I started my own company. Just solving real problems for real people.

(Is that cliché? Man, that sounds cliché. But, I guess its true so 🤷‍♂️)

To keep our focus on what matters, our process looks more like this:

1️⃣ Find the real problem (not the one written in the Jira ticket)
2️⃣ Build an MVP fast
3️⃣ Get feedback (usually some more features)
4️⃣ Iterate
5️⃣6️⃣7️⃣ Client happy. Ship it. Send the invoice

No red tape.

(Unless the client sells gift wrapping… then maybe, yeah. Some red tape.)

“Vibe coding” is Collins Dictionary’s Word of the Year

✅ The good: more people than ever are being exposed to coding. That’s exciting.

❌ The bad: we don’t yet know the long-term effects - i.e. poorly written, AI-generated code could mean major security breaches and costly maintenance down the line.

Double-edged sword.

Curious - where do you fall on this? Excited or skeptical?

I won’t @ the company.

But some chatbots do more harm than good!

I can’t share my actual screenshots (they mention their name), but so you can get an understanding of my experience with a pretty well-known company’s chatbot last week…

Check out my image for this post.
Yeah, that was basically it.

And this company is massive! Makes me question all the companies completely outsourcing their customer service.

VP of Engineering

- Employed AI technologies to enhance and optimize business processes
- Lead the software engineering teams to develop and deliver high-quality software, aligning with product requirements and fostering a collaborative team culture.
- Oversaw recruitment, career development, and performance management for software engineers and managers, including coaching, mentoring, and team-building activities.
- Articulate and execute a clear technical vision, managing the development process across multiple product teams and roadmaps.
- Establish and lead the strategy for system design, architecture, and coding practices, ensuring standardization and quality across software projects.
- Ensure adherence to security protocols and data privacy standards in all software engineering practices and solutions.
- Provide technical leadership and strategic guidance to product managers and engineering leadership, mediating conflicts and removing technical roadblocks.
- Define and lead Agile development processes, overseeing sprint planning, execution, and continuous process improvement.
- Manage software engineering schedules and resources, ensuring timely and successful delivery of product releases and iterations.
- Collaborate with product teams and business stakeholders to align software development with product KPIs and business objectives.

Director Of Engineering

Technical Leadership
- Lead evolution of NOVA’s cloud infrastructure by facilitating discussions and developing NOVA’s technical roadmap
 - Provide recommendations on infrastructure improvements to deliver consistent value while ensuring throughput and quality code is in line with expected goals
 - Oversee the design and evolution of NOVA’s infrastructure including developing and implementing creative solutions to support ETL pipelines  and cross department business strategies
 - Drive efforts to optimize network performance by growing and modifying existing networks, leveraging new and emerging technologies in support of application services
 - Oversee NOVAs’ network security to ensure optimal network safeguard processes are in place

Team Leadership
 - Lead direction and build out of NOVA’s Data Team by driving strategy and conducting technical interviews
 - Ensure implementation of best practices and adoption of new technologies within Data Team by conducting code reviews, hosting knowledge transfer meetings, and building out a documentation repository
 - Coordinate and lead training opportunities that will further accelerate the growth of the team in areas of need
 - Evangelize a microservice based architecture by utilizing Serverless Framework for ETL and Inference pipelines
 - Architect and implement automated CI/CD for all NOVA microservice's

Sr. Cloud Architect, Team Lead

Red Door Interactive

- Responsible for architecting and implementing Cloud Solutions.
- Reduce deployment process time for client web properties by implementing a standard CI/CD solution using AWS Services Code Build, Code Deploy, Code Pipeline, S3, Code Commit, and BitBucket
- Migrate client's web presence from on premise to the could utilizing AWS Services including but not limited to: Elastic Beanstalk, EC2, ElasticSearch, Application Load Balancer, ECS, S3, CloudFront, ElastiCache
- Facilitate requirements gathering process from elicitation and refinement to maintenance by leveraging Jama for managing and trace-ability.

Sr. Dev Ops Engineer

-  Involved in requirements gathering process from elicitation, refinement, and maintenance.
-  Reduce deployment process time for client web properties by implementing a standard CD (continuous deployment) solution using AWS services.
-  Build and maintain client web properties in ASP.NET and PHP; adhering to requirements and making recommendations based on best practices and business goals.

Marketing Technology Engineer

Ackmann & Dickenson, Inc.

- Responsible for building and maintaining features for ASP.NET/C# application.
- Collaborate with developers to write detailed requirements and architect solutions using a MVC design pattern
- Lead backend Magento developer responsible for site architecture, and custom extension builds

Software Developer

Irish Titan

- Lead backend Magento developer responsible for site architecture, and custom extension builds
- Tech lead on Magento and Drupal projects, providing oversight to developers and assisting in skill growth
- Collaborating with developers and online managers to complete projects on time and within budget

Web Developer

First Net Impressions

Develop and maintain client websites using PHP, HTML, CSS, and JavaScript.

Prime Advertising & Design

Responsible for updating and maintaining client websites, create and obtain photographs and graphics for a website, work with code, SMC, and ElementZ to build and edit sites, meet with clients to gather information on what their expectations are.

Web Design/Multi-Media Intern

The Spectator

Called businesses within my assigned route to sell advertising space in the newspaper, met with clients to discuss an advertising plan throughout the semester, created ads for businesses

Advertising Sales Representative

As a technology leader with a background in software engineering and solutions architecture, I am passionate about building high-performance teams with low attrition and high engagement. My experience includes motivating engineers to tackle complex problems and empowering them to innovate. I am also skilled in managing cross-functional teams, analyzing data, and making strategic decisions based on key insights.

In addition to my technical expertise, I am committed to driving consistency, quality, and security through the creation of reusable software components. I believe that this approach is essential for scaling and ensuring the success of any engineering organization.

Outside of work, I enjoy staying up to date with the latest trends and technologies in the industry. I am always looking to connect with like-minded professionals and expand my network.

Jamie Schiesel

If you’re measuring AI impact in lines of code, you’re doing it wrong.

I’ve heard too many engineering leaders say, “We’re now generating 50,000 lines of code per week.”

My response: What did that actually do for the business? How did it impact product quality?

We all know AI can write. Ask it to document something and it’ll hand you a novel.

AI isn’t about output volume, it’s about outcome quality. More code isn’t the goal. Better decisions, faster learning loops, cleaner designs, and fewer bugs are.

The real value shows up in places most teams never measure:
- How quickly an engineer can validate, scope and plan a piece of work
- How well they use AI to explore trade-offs
- How much distraction and rework AI removes from the process

None of that shows up in token counts, commit totals, or line counts.

So what should you track? 

Stick with the metrics you already know and love: cycle time, lead time, defect rates, and incident recovery....then layer in AI usage. Are your engineers weekly users? Daily? Hourly? And how does that correlate with the core engineering metrics you care about?

If you want real impact, stop counting code and start measuring how AI is changing the way your teams think, decide, and deliver!

Technology Leader | Driving Innovation | AI Enablement

taplio

The Battle

Christopher Fitkin

Jamie Schiesel

Followers

Posts

Engagements

Likes

Performance ScoreChristopher Fitkin's LinkedIn Performance

Performance ScoreJamie Schiesel's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Christopher Fitkin

Jamie Schiesel

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);}Christopher Fitkin's LinkedIn Performance

Performance ScoreJamie Schiesel's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreChristopher Fitkin's LinkedIn Performance