Talk to us

About IsNull

About IsNull Softworks, the embedded QA and product ownership partner for small software teams. Technical, collaborative, and accountable for the work.

For engineering leaders at established small software teams and the fractional CTOs who support them, we prioritize bugs, features, and documentation so the highest-impact work ships first.

In code, IsNull() checks for something that’s missing. We do the same for software teams.

  • Nobody owns testing? We do.
  • No backlog owner? We run it.
  • Developers at capacity? We add hands.
  • AI on the roadmap? We build it in.

Our story

Why we focus on QA, documentation, and product ownership. AI made writing code faster. Checking it didn’t keep up.

Our experience grew in event-industry software, where complicated workflows, changing requirements, and live deadlines are normal, and where a bug on show day isn’t an option.

As AI changes how software gets written, code arrives faster than anyone can check it. The gaps move to QA, documentation, and product ownership. That’s where we work: embedded in small teams, making sure what ships is what was meant, and that the most important work goes first.

CodeAI-assisted, fast
MissingIsNullProduct
MissingIsNullQA
MissingIsNullDocs
ReleaseWhat was meant
Illustration. Code gets written faster than ever. Product ownership, QA, and documentation make sure it’s what was meant.
Andres Mendoza, CEO of IsNull Softworks

Leadership

Andres Mendoza, CEO

Andres leads IsNull Softworks and every client engagement. He brings a background in software development and product ownership, and he’s the person who connects your goals to a workable scope, clear communication, and a practical plan.

You’ll work with Andres from the first intro call onward, with our engineers working directly inside your team.

IsNull Softworks on LinkedIn

How we show up

Five things you can expect from us

  • Capable

    Senior technical judgment on QA, product, and engineering, applied to the problem you actually have.

  • Small team, big impact

    Close enough to the work to own it, focused on the changes that move your release forward.

  • Trustworthy

    We say what was checked, what wasn’t, and what still needs a decision.

  • Technical partner

    We work inside your sprint and your tools, alongside your developers and product lead.

  • Collaborative

    Stakeholders, developers, and end users all get heard, and everyone hears back on what shipped.

What you get

What embedded QA and product ownership deliver. Fewer surprises at release, and work that ships in order of impact.

Every sprint ends with evidence you can act on: what was checked, what was fixed before customers saw it, what shipped, and what’s documented. You get the results without another tool to manage.

  • Releases checked before they ship
  • Coverage that grows every sprint
  • The highest-impact work ships first
  • A clear verdict on every pull request
  • Docs that match what shipped
  • AI that knows when to hand off

How we work

How an engagement with IsNull works. Small steps, clear conversations, and a written plan first.

  1. 1

    Intro call

    We talk through your team, your release cadence, and where quality or ownership is slipping. A URL or a walkthrough is usually enough to start.

  2. 2

    Written plan

    Deliverables, boundaries, access, timing, and cost, agreed in writing before work begins.

  3. 3

    Join your workflow

    We work in your sprint and your tools. Checks run as part of your workflow, and our engineers review every result.

  4. 4

    Review and report

    You see what changed, what we found, and what’s still open, and decide together what comes next.

Book an intro callSee our services

Security and access

How we handle access, data, and changes

Boundaries are agreed before we touch anything, and people stay responsible for every change.

  • Agree the access and test scope

    We identify the environments and journeys we’re allowed to use. Test accounts and synthetic data are preferred. Anything that could affect real customers, payments, or messages gets explicit boundaries.

  • Decide how information is handled

    Source code, screenshots, and test data may be part of an engagement. Hosting, model providers, access, retention, and sharing are agreed at onboarding and recorded in the scope.

  • Keep people responsible for changes

    Automated checks gather evidence; our team reviews the work with your process in mind. Repository access, approvals, and release responsibilities are set before that workflow is turned on.

  • Be clear about what we offer

    QA is delivered as a managed service by our team, not sold as self-service software. We don’t claim SOC 2 certification, and automated testing doesn’t establish security or regulatory compliance on its own.

Questions

Questions about working with IsNull

Can we start without sharing our repository?
Often, yes. An authorized review of a public or test URL can be a useful start. Source-based documentation, code changes, and isolated builds need more access and setup, agreed in the written plan.
Is there a free pilot?
We haven’t published a free-trial offer. We agree the scope, pricing, and what would make a first engagement worthwhile before you commit.
What happens when an engagement ends?
We review the work together and agree the handoff. Ongoing work, access, and deliverables are only continued if you choose to, and are agreed explicitly.
Where is IsNull Softworks based?
IsNull, LLC is a US company, and we work with engineering teams across the US.
Who will we work with?
Our CEO, Andres Mendoza, leads every engagement from the first call, with our engineers working directly inside your team.
Have a different question?
Send it with a few details about your team and we’ll answer it directly.
Ask us

Next step

Put QA and product ownership on your team this quarter.

Tell us where releases are slipping. We’ll map out how an embedded team would help, in writing, before you commit to anything.

Book an intro call

Field notes on QA and shipping

Occasional, practical notes for engineering leaders. No spam.