Venture Overview
In Orlando, circa 2007, I lived three lives daily: corporate IT specialist at KMG by day, ambitious Rollins College student by evening, and bass guitarist in dimly lit venues by night. Nobody plans to start a business this way—stretched thin across disparate worlds, running on coffee and ambition, sleeping only when absolutely necessary.
But that's the thing about entrepreneurship—it rarely announces itself with fanfare. For me, it arrived disguised as a casual conversation between bass riffs at a downtown Orlando club called The Social. "You fix computers, right? Our office network is a disaster," said a guy who'd been nodding along to our second set. By Monday, I had my first potential client.
The Whittaker Group began as little more than letterhead and business cards I designed at 2AM after finishing a term paper. The logo—embarrassingly amateur looking back now—took me six iterations and felt like Picasso-level brilliance at the time. The S-Corp registration with Florida's Department of State cost money I didn't really have, but made the whole thing feel legitimate in a way that mattered, if only to me. What I couldn't articulate then but understand now: I wasn't just starting a business—I was creating a vehicle to test whether my technical skills had value outside the safe confines of corporate employment.
This essay isn't about overnight success or entrepreneurial genius. It's about what happens when you're foolish enough to say "yes" to opportunity while smart enough to figure things out along the way. It chronicles how a fragmented schedule—KMG's technical demands, Rollins' theoretical frameworks, and Orlando's music scene's lessons in self-promotion—created an accidental laboratory for business creation that would change everything about how I understood professional value.
Finding Value in the Margins
The precise moment I became an entrepreneur is impossible to pinpoint. No single decision separated the before from the after. Instead, there were dozens of small shifts—each nudging me from employee to something... more.
It started with favors—the universal entrepreneurial gateway drug. A drummer from my weekend band needed help with his home recording setup. A classmate at Rollins couldn't figure out why her laptop kept crashing during presentations. The barbershop owner who always came to our shows mentioned his ancient POS system was giving him fits. Each problem I solved led to another introduction, another opportunity, another moment where someone looked at me and said, "You know about this stuff, right?"
What I didn't realize then: these weren't just technical problems. They were market signals. Every frustrated complaint about "my expensive IT guy who doesn't explain anything" or "that company that charges $200 just to show up" revealed a gap between what traditional tech services provided and what customers actually wanted.
"Man, you should start charging for this," said Marcus, a saxophonist whose entire digital music library I'd just rescued from a failing hard drive. "You explain things without making me feel stupid. That's worth something."
It was the third such comment in a week. And like compound interest, these suggestions were beginning to accumulate into something that demanded attention.
The awakening wasn't about technology at all—it was about translation. I could speak fluent geek at KMG, explain business concepts at Rollins, and translate both into plain English for everyone else. This skill wasn't particularly impressive in any single domain, but in the spaces between them, it became surprisingly valuable. The realization hit me during a late-night coffee run between a server upgrade and band practice: perhaps the most valuable opportunity wasn't climbing any particular ladder but building bridges between them instead.
Bread Bowls and Business Plans
The transition from hobby to business happened on a Tuesday night at Panera Bread near the Rollins campus. I'd just finished a brutal finance exam and was rewarding myself with soup in a bread bowl when I opened my notebook and wrote: "The Whittaker Group – Services."
Below that headline, I scribbled what would become my initial service offering:
- Server Support & Configuration ($120/hr)
- Network Design & Troubleshooting ($100/hr)
- Web Development ($75/hr + hosting)
- Emergency Support ($150/hr, 2hr minimum)
These weren't numbers I'd scientifically calculated. They were educated guesses based on what I'd gleaned from overhearing conversations at KMG about billable rates, adjusted downward because I had neither the overhead nor the experience of established firms. The pricing strategy was simple: enough to be taken seriously but not so high that I couldn't deliver commensurate value.
What's fascinating in retrospect is what this makeshift menu represented: not just services, but the specific intersection of what I could confidently deliver and what the small business market desperately needed but wasn't getting from enterprise-focused IT providers. I wasn't attempting to compete with established firms on their terms; I was carving out an entirely different value proposition based on accessibility, transparency, and personal attention.
By dessert (chocolate chip cookie), I'd sketched a logo that looked suspiciously like something from a late-90s clip art collection. By the drive home, I'd decided this was actually happening. By midnight, I'd registered a domain name and begun the paperwork for a business license.
Nothing makes entrepreneurship feel real quite like spending money you don't have on things that exist only in your imagination. Within a week, I'd invested nearly $700—a small fortune for a stretched-thin student-employee-musician—on basic business infrastructure: legal formation as an S-Corporation (chosen primarily because it sounded most legitimate), business cards from a local print shop (which arrived with a slight but noticeable misalignment that I pretended was an intentional design choice), and a simple website built using skills I'd picked up fixing other people's digital problems.
I wrote my "About Us" page using the royal "we" despite being a company of exactly one. This wasn't intentional deception—it was aspirational positioning. I wasn't selling just my time; I was selling the promise that someone would actually answer when things went wrong, a surprisingly rare commitment in the IT services space of 2007.
My kitchen table became command central—papers arranged in neat piles, a freshly purchased QuickBooks license awaiting its first entry, and a yellow legal pad listing potential clients culled from various social circles. The fear was constant but oddly energizing; each decision felt like another step on a high wire without a net.
Bass Lines to Bottom Lines
My first major client opportunity arrived through an unexpected channel—a chance conversation after a particularly well-received bass performance at one of Orlando's upscale venues. Jim Strasberg, co-owner of First Builders, a commercial construction firm in Altamonte Springs, mentioned his company's technology frustrations during set break.
"We've got files everywhere, no backup system, and our last IT guy disappeared after cashing our check," he explained. "But you probably don't do that kind of work."
The moment demanded immediate decision: acknowledge my limited business history or project confidence despite it. I chose a middle path.
"Actually, that's exactly what The Whittaker Group specializes in—enterprise-level solutions for small to medium businesses," I heard myself say, simultaneously terrified and exhilarated by my own certainty. "Why don't we schedule a proper consultation next week?"
What followed was three days of intensive preparation—researching optimal server configurations for construction businesses, developing detailed proposal templates, and calculating pricing models that wouldn't undervalue my expertise while remaining competitive. When I arrived at First Builders' office—a converted warehouse with architectural plans covering every surface—I carried a leather portfolio containing the most meticulously prepared document of my professional life.
"This proposal outlines a comprehensive solution," I explained, walking Jim and his partner Jordan through recommendations for a Dell PowerEdge 840 server running Windows 2003 R2, configured for file sharing, DHCP, and terminal services. "Implementation would require approximately five consulting hours at $120 per hour, plus hardware costs."
The specificity and confidence of my presentation masked the butterflies in my stomach. When they signed the proposal that same meeting, I realized I had crossed an invisible threshold—from someone who helped with technology to someone who provided technology solutions. The distinction was subtle but transformative.
The actual implementation happened on a Saturday—the only day I could block off completely from my other commitments. I arrived at 7AM with the newly delivered server, a toolkit meticulously organized the night before, and enough anxiety to power a small city. By 3PM, I had configured user profiles for all seven employees, migrated scattered files from various workstations into a coherent shared folder structure, established automated backup procedures to their external drive, and conducted an impromptu training session for the office manager.
"You make this all seem so... normal," Jim said as I packed up. "Our last IT guy acted like he was performing black magic whenever he touched our computers."
I didn't admit that my apparent calm came from over-preparation rather than experience. I'd literally practiced server configurations in my apartment three times before attempting it live. The price of appearing effortless is often invisible effort.
Finding Purpose in Service
The First Builders project transformed The Whittaker Group from concept to reality, but it also forced an unexpected reckoning with deeper questions. As I deposited my first substantial business check, I realized I needed to decide what this venture was actually for.
Was this just a sophisticated side hustle to supplement my income? A practical laboratory for applying academic concepts? A bridge to eventual full-time entrepreneurship? The answer wasn't obvious, but it mattered immensely for every subsequent decision—from which clients to pursue to how much time to invest in growth.
The clarity emerged gradually through a series of small choices: declining a lucrative opportunity that would have required missing classes, investing income in professional certifications rather than marketing, focusing on relationship-building rather than transaction volume.
I didn't want to build an IT services company that happened to be mine; I wanted to create a vehicle for expressing a particular vision of how technology should serve people: transparently, educationally, and with genuine care for outcomes beyond billable hours.
This realization reshaped my approach to client interactions. I began each engagement with extensive conversations about business processes rather than technical specifications. I avoided jargon religiously. I included training time in every proposal—not as an add-on service but as an integral component of implementation.
When Jim Strasberg referred me to another construction company facing similar challenges, I spent our first meeting asking about their workflow pain points before mentioning any technical solutions. This approach wasn't just philosophical—it generated tangible business outcomes. Clients who understood their own systems requested fewer emergency interventions and made more strategic upgrade decisions.
My biggest "aha" moment came when a client explained that what he valued most wasn't the technical solution itself but the peace of mind that came with it. "I don't pay you to fix computers," he said. "I pay you so I can sleep at night knowing someone competent cares about our technology." That insight—that I was fundamentally in the anxiety-reduction business rather than the server-configuration business—changed everything about how I positioned and delivered services.
Lessons from Three Worlds
Running The Whittaker Group alongside my other commitments required constantly evaluating its performance against multiple metrics—not just financial returns but impact on my overall professional development. This wasn't a theoretical exercise but a practical necessity; any time invested in the business represented time unavailable for coursework, KMG responsibilities, or rejuvenating downtime.
I developed an informal evaluation framework that considered:
- Revenue generation (basic sustainability)
- Knowledge acquisition (skills I gained from each project)
- Network expansion (new connections and referral potential)
- Academic application (concepts that enhanced my Rollins work)
- Enjoyment factor (whether I actually liked the work)
This multi-dimensional assessment helped balance short-term opportunities against long-term goals. A lucrative but tedious website maintenance contract might score high on revenue but low on knowledge acquisition and enjoyment. Conversely, a complex server migration for a promising startup might offer modest immediate compensation but exceptional learning value and network expansion.
What emerged was a surprisingly sophisticated portfolio approach to client selection. Each project didn't need to maximize every dimension, but the overall client mix needed to deliver balanced value across all metrics. This mindset—evaluating opportunities against multiple simultaneous objectives—became a transferable skill that proved valuable long after The Whittaker Group itself.
Perhaps the most unexpected benefit of this entrepreneurial experiment was how it dissolved artificial boundaries between my otherwise compartmentalized worlds. Knowledge flowed freely between domains:
- Technical challenges at KMG informed how I structured client solutions
- Academic theories from Rollins provided frameworks for business decisions
- Client interactions became case studies for classroom discussions
- Stage presence developed through music performances translated to client presentations
- Time management skills honed by necessity became applicable everywhere
The Whittaker Group became a central node connecting previously isolated knowledge spheres, creating value through integration rather than specialization. This wasn't intentional design but emergent function—the business became valuable precisely because it sat at the intersection of multiple domains rather than deeply within any one.
A particularly vivid example: for a final project in my Operations Management course, I analyzed The Whittaker Group's service delivery process, identifying bottlenecks and implementing changes that reduced average project completion time by 22%. The professor praised the analysis; what she didn't know was that I implemented the recommendations the very next weekend, transforming theoretical academic work into immediate practical benefit.
Reflections
Looking back from the vantage point of many subsequent ventures, I recognize that The Whittaker Group represented something more significant than a first business attempt. It was an entrepreneurial laboratory where the stakes were real but manageable, where failure would sting but not destroy, and where the primary education wasn't about technology or business mechanics but about myself.
I learned that entrepreneurship isn't a job title but a mindset—a particular way of seeing gaps between what exists and what could be, then constructing bridges across those gaps. The technical skills that made me valuable at KMG were only the raw material; the entrepreneurial act was recognizing how to repackage and repurpose those skills for different contexts.
More fundamentally, The Whittaker Group taught me that professional identity doesn't need to be singular or fixed. The traditional narrative suggests we must choose—employee or entrepreneur, specialist or generalist, academic or practitioner. What I discovered instead was the power of "and"—that occupying the spaces between established roles creates unique opportunities for value creation.
The business itself evolved over subsequent years, shifting focus as my own interests and market demands changed. But its most enduring impact wasn't measured in revenue or client logos—it was in reframing how I understood professional possibility. Entrepreneurship wasn't separate from my other pursuits; it was the thread that connected them, the lens that revealed how apparently disparate skills and interests could combine into something greater than their sum.
This lesson—that boundaries between domains need not be barriers but interfaces where value is created through translation and integration—has informed every professional decision since. The most interesting opportunities rarely exist squarely within established categories but emerge at their edges, where different worlds connect and new possibilities become visible to those willing to navigate the spaces between.