InTech Ideas
How We WorkPodsAboutInsightsBook a Call
How We WorkPodsAboutInsights
Book a Call

Company

AboutHow We WorkPods

Resources

InsightsArticlesSubstack

Connect

[email protected]Book a Call

Clarity before code. Relationships before contracts.

Privacy·Terms·Cookies

© 2026 InTech Ideas. All rights reserved.

Built by People Who Have Been There.

InTech Ideas started with a conviction: the best software comes from teams that care about each other and the product they're building.

How We Got Here

Skip Marshall and Chuck Griess didn't start InTech Ideas because they wanted to build another outsourcing company. Skip brings the product strategy and business lens -- asking "what problem are we actually solving?" before anyone opens an IDE. Chuck brings the systems architecture and technical rigor. Together, they kept watching the same pattern repeat: companies hire engineering teams, hand over vague requirements, and wonder why the product doesn't land.

The traditional outsourcing model made it worse. Teams measured by hours billed have no incentive to ask hard questions or push back on unclear specs. The relationship is structurally adversarial -- the client wants less hours, the vendor wants more. Nobody wins except the people writing the invoices.

So they built InTech to be the opposite. Relationship first. Engineers embedded in client teams, not isolated in a separate timezone. A methodology -- CRAFT -- that ensures every hour of work points at a clearly defined outcome. Not because process is fun, but because clarity is the difference between building the right thing and building the thing right.

"We didn't pivot to AI. AI validated what we'd been building all along."

Then AI changed the game. Suddenly code generation could produce working software fast -- but it could also build the wrong thing at unprecedented speed. The companies that would win weren't the ones with the best AI tools. They were the ones with the best clarity about what to build and why. CRAFT was built for exactly this moment.

InTech started as a nearshore development partner. Today it's a product engineering firm built for the AI era -- with teams in the US and Latin America, a proprietary methodology, and a weekly podcast where Skip and Chuck argue about all of it. The conviction hasn't changed. The tools got better.

What We Believe

These aren't aspirational statements. They're how we make decisions, who we hire, and how we show up for every client.

People over Technology

Technology is powerful because of what it enables people to do -- not the other way around. We believe the best software comes from people who are creative, adaptive, and freed from mundane work. AI is a tool that amplifies human judgment. It doesn't replace it.

Relationships over Projects

The days of transactional outsourcing are over. We build partnerships for the long term -- where your engineer knows your team by name, understands your product deeply, and is invested in your success. Not because a contract says so, but because they care.

Collaboration over Silos

Successful teams engage everyone -- employees, clients, end-users, and partners. We measure engagement and satisfaction across the entire ecosystem, not just within our own walls. Your team is our team.

Curiosity over Indifference

Lifelong learning is no longer optional. The industry moves too fast for anyone to coast. We stay curious because the moment you stop learning, you start building yesterday's solutions. Our podcast, our methodology, our culture -- all driven by a refusal to settle for what we already know.

Meet Skip & Chuck

InTech is founder-led. That means the people who built the methodology are the same people you'll talk to on a discovery call.

Photo of Skip Marshall

Skip Marshall

CEO & Co-Founder

Skip thinks in product strategy, business outcomes, and client relationships. He's the one asking "what problem are we actually solving?" before anyone opens an IDE.

His background spans product management, business development, and operational thinking. He built InTech because the outsourcing model was broken -- and the fix wasn't better engineers, it was better clarity about what to build and why.

Skip leads InTech's strategic direction, manages client relationships, and co-hosts the weekly podcast.

The best engineering in the world is wasted if you're building the wrong thing.
Photo of Chuck Griess

Chuck Griess

CTO & Co-Founder

Chuck thinks in systems architecture, technical rigor, and engineering craft. He designed the CRAFT operating system and the Pro-Neering methodology that powers every InTech engagement.

His background runs deep in full-stack engineering, infrastructure, and disciplined systems thinking. He built InTech's technical DNA around a conviction: AI should amplify engineering judgment, not replace it. Every decision should be explicit, documented, and measurable.

Chuck oversees technical strategy, mentors the engineering team, and brings the contrarian technical perspective to the podcast.

If you can't explain why you made a technical decision, you didn't make one -- you guessed.

Skip brings the business lens. Chuck brings the technical lens. The tension between strategy and craft is what makes the methodology work -- and what makes the podcast worth listening to.

Your Team. Not a Resource Pool.

Every InTech engagement is staffed with dedicated people -- not names drawn from a bench. Your engineer is your engineer. Your PDL is your PDL. They know your product, your team, your goals, and your constraints. They're not context-switching between five clients.

Your team is online when you are. Eastern time zone alignment means real-time collaboration, not overnight handoffs. No asynchronous confusion. No waiting until tomorrow for an answer you need today.

Behind every engagement is a support layer -- DevOps, QA, and UI/UX designers -- all operating under the CRAFT methodology. Your dedicated engineer isn't working alone. They're backed by a team that shares the same commitment to outcomes.

What Makes InTech Engineers Different

Typical OutsourcingInTech Ideas
Client dedicationShared across multiple clientsDedicated to your product exclusively
Starting approachStarts coding immediatelyStarts with understanding your intent and outcomes
Work modelWorks from a ticket queueEmbedded in your team's daily workflow
Knowledge depthKnows the codebaseKnows the codebase, the product, and your team
ReportingReports hours workedReports outcomes against intent
ContinuityReplaced without noticeBuilds context that compounds over time

US Leadership. Latin American Engineering. Eastern Time Alignment.

Headquarters

Tampa Bay, Florida

Strategic leadership, client relationships, and product strategy. Close to our clients, in their time zone, and always available.

Engineering Operations

Panama

Full PEO employees with benefits and career development. Not contractors. Not rotating. Professionals who build careers at InTech -- all on Eastern time.

Let's Start With a Conversation.

We'll tell you how we work. You'll tell us what you're building. And we'll both figure out if this is the right fit.

Book a Discovery Call

Or email us directly: [email protected]

Read How We Think

Ideas, frameworks, and perspectives on product engineering, AI, and building what matters — from Skip and Chuck at InTech Ideas.

Latest ArticleThe $50k Prototype Trap: Why Your MVP Cost Too Much and Delivered Too Little

The demo worked. The product didn't. Here's the question nobody asked.

Mar 31, 2026·Skip MarshallRead on Substack →
Mar 24, 2026Borrowed from Distributed Systems: Coordination Patterns for AI-Assisted TeamsFive patterns from distributed systems that explain why your AI-assisted team keeps tripping over it...Mar 17, 2026Field Notes: How We Stopped Re-Litigating Every DecisionWhat happened when we started writing down what we actually decided — and why.See all articles on Substack →