Charly's daily system, Tomas's founder focus, and recurring checklists live here — where they actually persist and sync across devices.
🎯 Direct Outreach — The New Model
We don't wait for inbound. We find companies where software = more money, then reach out with a clear value prop. No platforms, no competition, no race to the bottom.
🏢 Target Business Profiles — Who to Find
Ranked by revenue impact + conversion probability. Use these to filter leads from Apollo, LinkedIn, and the AI lead gen tool.
Cover Letter Templates
Specialized by role. Click Copy — customize [brackets] before sending. Always link nlpointer.com first.
NullPointer LLC
AI-Augmented Senior Engineering · We Build. We Own. We Deliver.
We are not a dev shop. We are not freelancers. We are a product-building unit — the technical equivalent of a co-founder team that shows up with conviction, takes ownership, and does not leave until the job is done right.
Our Core Principles
Before writing a single line of code, we ask: what does success look like from the client's perspective — not ours? We understand their users, their business model, their deadlines, and their fear of failure. We do not optimize for our convenience. We optimize for their outcome.
We only take on work we are confident we can win. If we don't believe in the project, we say so. If the scope is unclear, we clarify before committing. We don't sign contracts we can't keep. Taking on bad work is a failure of integrity, not just execution.
If we committed to it, we deliver it. No excuses, no redirecting blame, no redefining scope after the fact. If something goes wrong — and in software, something always does — we own it, fix it, and make the client whole. Accountability is the only currency that compounds.
Meeting the spec is the floor, not the ceiling. We look for the one thing the client didn't ask for but will thank us for — a performance improvement, a UX detail, a piece of documentation that saves them three calls. We don't ship the minimum. We ship the best we can do in the time we have.
Asking for equity is not greed — it is a public statement of belief. When we ask for a stake, we are saying: we are betting on this the same way you are. We have worked for minimum cash until delivery, taken equity over retainer fees, and reduced our rate for founders whose ideas we believe in. Skin in the game is our default mode.
Inspired by how the best-run companies operate: speed is not recklessness, it is respect for opportunity cost. Every day a product isn't shipped is a day a competitor could move. We use AI tooling, clear architecture, and zero tolerance for process theater to move 3–5x faster than traditional teams — without cutting corners on quality.
"Best practices" are yesterday's solutions to yesterday's problems. We reason from first principles: what is the actual goal? What are the real constraints? What is the simplest thing that could work at scale? We question requirements. We eliminate unnecessary complexity. The best solution is often the one nobody asked for because nobody thought to simplify that far.
Talent is common. Relentless work ethic is rare. We show up early, stay late, and treat every client's deadline as our own. We don't coast. We don't mail it in on Fridays. The teams that build the most enduring products are the ones that outwork the field — not by 10%, but by an order of magnitude. That is our standard.
We do not accept "good enough." A bug that ships is a broken promise. Code without tests is a liability we're handing the client. A dashboard that's confusing is a product we didn't finish. We maintain high standards because standards are contagious — and so is the lack of them. We would rather push back on scope than ship something we're ashamed of.
Anyone can build a demo that impresses in a meeting. We build systems that hold up at 100x the load, survive team turnover, and don't require the original developer to maintain them. We think about versioning, observability, failure modes, and governance from day one — because the hard problems in software aren't features, they're architecture.
Our Promise to Every Client
✦ We will tell you the truth about your project, even when it's uncomfortable.
✦ We will not start work we don't believe we can finish excellently.
✦ We will treat your money like it's ours — because sometimes it is.
✦ We will never hide behind technical jargon to avoid accountability.
✦ We will ask for equity when we believe in what you're building — because that's what partners do.
✦ We will deliver more than the spec asked for and less of the bloat you didn't need.
✦ When something goes wrong, you will hear it from us first, along with a plan to fix it.
The Team
💰 How to Sell NullPointer
A system, not a talent. Everyone on this team can sell.
Selling is not a gift. It is a teachable, repeatable process. A 30-year entrepreneur who built 19 companies and invested in 78 startups broke it down — this page distills that playbook specifically for NullPointer. Read it. Internalize it. Use it.
1. The Mindset — Selling Is a System
"There's no such thing as people who are good at selling and people who aren't — just people who haven't been taught the system."
— The source of this entire playbook
Most engineers think they can't sell because they conflate "selling" with manipulation or extroversion. That's wrong. Selling is simply helping someone understand why what you have solves their problem better than their alternatives.
- • "I'm not a salesperson"
- • "I'll let the work speak for itself"
- • "I don't want to be pushy"
- • "If they want it, they'll reach out"
- • "I'm helping them solve a real problem"
- • "Clarity and communication is my job"
- • "Persistence is respect for their time"
- • "Nobody buys what they haven't heard about"
2. Lead with Purpose, Not Price
People buy into the mission before they buy the service. When you sell NullPointer, you are not selling hours — you are selling ownership, conviction, and outcome. The "why" is the hook.
NullPointer's "Why" for Any Pitch:
- →We are not contractors. We are a co-founder-caliber team that takes technical ownership and delivers outcomes — not activity.
- →We work with founders and teams who want senior-level engineers who show up with initiative, not hand-holding.
- →Our goal is to be worth more than we cost — every single engagement.
When your why is clear and genuine, it disarms the price objection before it comes. People don't negotiate with someone they believe in — they try to find a way to say yes.
3. Charge by Outcome, Not by the Hour
Hourly rates commoditize you. They invite comparison to Upwork freelancers. Outcome-based pricing reframes the conversation from "how much does it cost?" to "what is this worth to my business?"
"We charge $150/hr and estimate 200 hours." → Instantly sounds like a contractor. Client calculates hours, questions efficiency, shops around.
"We deliver X fully built and deployed for $Y, with these specific milestones." → Client buys the outcome. You control your own efficiency.
"For ongoing work, we prefer a monthly retainer + equity stake." → You become a partner, not a vendor. Aligns incentives long-term.
4. The Pitch — What to Actually Say
A pitch is not a monologue. It is a structured conversation. Follow this sequence:
5. Outreach — Specificity Wins Every Time
Generic outreach is noise. Specific outreach is signal. The difference between a 0% response rate and a 30% response rate is specificity — showing you read the room, did your homework, and have something real to say.
"Hi, I'm Tomas from NullPointer. We're a software development firm specializing in full-stack development with over 10 years of experience. We'd love to discuss how we can help..."
"Hey [Name] — saw your post about scaling your ingestion pipeline. We just solved the same problem for a healthcare SaaS — cut their processing time 80%. Quick 15 mins this week?"
Rules for Every Outreach Message:
- →Reference something specific about them (their post, their product, their job description)
- →Lead with their problem, not your credentials
- →One clear ask at the end — not three options
- →Under 5 sentences. If it needs more, it's not ready.
- →Always link nlpointer.com — first credibility check is your site
6. Handling Objections — The Real Conversation
Objections are not rejections — they are requests for more information. Every objection is a question in disguise. Here are the ones we face most and how to handle them:
Don't defend your price — reframe the cost of NOT solving the problem. "What does it cost you per month to keep this problem unresolved? If we fix it in 6 weeks and it runs for 2 years — is $40k expensive or cheap?" Then go quiet.
"Absolutely — you can. What we can't compete with on price, we compete with on outcome. Most clients who've tried both come back because junior work needs senior cleanup. We skip that step." Then offer a smaller scoped engagement to prove it.
"Totally understand — when do you think you'll be ready? I'll put a reminder to follow up then." Always get a specific date. "Not yet" with a date is a warm lead. "Not yet" without one is a dead end — but still follow up in 30 days.
"That's great — we often work alongside internal teams as an extension, especially for architecture decisions, performance bottlenecks, or shipping new features faster. Is there a specific bottleneck your team is fighting right now?"
This is often a polite stall. "Happy to — what specific piece would be most useful? I want to make sure I send the right thing." Forces them to engage. If they still want a general PDF, send it with a specific follow-up booked.
7. Follow-Up — The Fortune is in the Follow-Through
Most deals are lost not because of "no" — but because someone stopped following up. Research consistently shows deals close after 5–12 touchpoints. Most salespeople give up after 2.
Follow-Up Cadence That Works:
Key rule: every follow-up needs a reason. "Just checking in" is weak. "Saw this and thought of you" or "We just shipped X and thought it was relevant" gives them something to respond to.
8. Personal Brand — Your Invisible Sales Team
Your personal brand is what people say about you when you're not in the room. In 2025, it is not optional — it is infrastructure. Every post, every project you ship publicly, every comment in a forum is a touchpoint for someone who might hire you.
- →Inbound leads that already trust you before the first call
- →Shortens the "who are you?" phase of every pitch
- →Justifies premium pricing — you're a known quantity
- →Compounds over time — posts from 2 years ago still bring leads
- →LinkedIn: Post 1x/week — a problem you solved, a lesson, a tool you built
- →GitHub: Public portfolio at github.com/nlpointerllc/Portfolio
- →Site: nlpointer.com is your first impression — keep it current
- →Niche down: "AI-augmented senior engineers" is more memorable than "dev shop"
9. Marketing vs. Sales — Know the Difference
Marketing generates awareness. Sales closes deals. They work together but they are not the same job — and confusing them wastes effort.
- • LinkedIn posts, GitHub presence, case studies
- • Job platform profiles and activity (Braintrust, Toptal, etc.)
- • Portfolio kept up to date and shareable
- • Consistent brand voice: "AI-augmented senior engineering"
- • PR: any time we ship something public — announce it
- • Direct outreach to specific leads in the pipeline
- • Cover letter and application quality per role
- • Follow-up cadence on warm leads
- • Proposal and scope conversations
- • Closing: asking for the yes, directly and confidently
10. Closing — Ask for the Yes
The biggest mistake non-salespeople make is never asking for the business directly. A great conversation that ends without a clear ask is a missed opportunity. Closing is not pressure — it is clarity.
"Based on everything we've talked about, I think we're a strong fit. Want to talk about kicking off in the next two weeks?"
"Would it be better to start with a focused sprint to prove the approach, or go straight to full engagement?"
"We have capacity opening up next month — I'd hate for us to miss the window if you're serious about this."
The Golden Rule of Closing
After you make the ask — go quiet. Don't fill the silence. The first person to speak after the ask is usually the one who concedes. Let them process. Their answer, whatever it is, moves you forward.