// About // The founder

Andrej Pilipović.
Operator, not consultant.

I started Ipsilon Solutions because the best systems I've ever seen were built by people who had to live inside them. I've spent the last three years embedded as a first technical hire at a venture-backed startup, building the IT, ops, and product plumbing that let a scrappy team scale into a real operation. Ipsilon is the next chapter: bringing that work to more teams who need a builder in the room.

Andrej Pilipović
// 01 Origin

Why Ipsilon exists.

Most early-stage startups don't fail at product. They fail at the operating system around the product. Onboarding is chaos. Tools don't talk to each other. Nobody owns the IT stack. SOPs exist only in one person's head. The CEO becomes the helpdesk. By the time the team realizes it, they're hiring around the problem instead of fixing it.

I spent three years watching, and building, the alternative. What a company actually needs in its first five years is an operator who can see the whole stack (product, IT, ops, people) and ship the scaffolding that lets the business grow without the founders having to babysit every system.

Ipsilon Solutions is built around that belief. We work as embedded operators for pre-seed, seed, and bootstrapped companies, the stage where a traditional consultant is too detached and a full-time hire is too heavy. We come in, map the mess, ship the fix, document the whole thing, and leave the team with a system they own.

We also believe AI belongs in the foundation, not the marketing. Every workflow we build is shaped around the question: where does an LLM genuinely reduce the manual load, and where is it just a shiny distraction? Usually the answer is: fewer places than people expect, and the ones that matter compound fast.

// 02 Operator snapshot

A rough shape of three years.

Directional, not definitive. The precise numbers live in the case study. The point here is the surface area of what embedded operator work actually looks like day-to-day.

3 yrs
Embedded at a single venture-backed startup
// First technical hire → department lead → chief-of-staff
3
Distinct roles held across the tenure
// IT, product ops, account exec + business unit lead
4
Continents in the team I supported
// US, Europe, Asia, South America
20+
SaaS platforms managed as a unified stack
// Workspace, PM, comms, telephony, BI, security
150+
SOPs authored and maintained
// IT, operations, partner, customer
50+
Integrations and automation pipelines
// n8n, API glue, LLM-assisted workflows
5,000+
L1-L3 support tickets resolved
// Scaling a helpdesk from zero to four-tier SLA
1 → 3
Grew IT from solo into a small internal team
// Hired, trained, handed off
// 03 Principles

How we work.

A short list that does a lot of filtering. If any of these feel wrong, we're probably not a fit, and that's fine.

01

The best system is the one simple enough to actually work.

If your team can't explain it to a new hire in ten minutes, it's too clever. We optimize for things that survive contact with real humans.

02

Ship in weeks, iterate forever.

Long design phases are where momentum goes to die. We lean toward the smallest thing that's obviously an improvement, then sharpen it live.

03

Automate the boring, not the nuanced.

LLMs and workflow tools are great at volume and triage. They're bad at judgment. We design so humans stay in the loop where it matters.

04

Docs are part of the product.

Every system we ship comes with a runbook. If it doesn't, it's not done. Your team should be able to run it without us next week.

05

No vanity tools.

We don't add platforms for the sake of looking serious. We rationalize, consolidate, and negotiate the stack down before we add to it.

06

Honest when things break.

Things will break. We tell you early, we tell you what we learned, and we write the post-mortem so it doesn't break the same way twice.

// 04 Engagement types

Three shapes of working together.

Most engagements start with a short diagnostic and evolve from there. Happy to shape the scope around what your team actually needs.

// 01 Audit

Stack & ops diagnostic

A focused two-week pass across your tools, processes, and spend. Written findings, prioritized fix list, and clear sequencing. Useful on its own, often a starting point for bigger work.

Duration2 weeks
// 02 Build

Project engagement

A defined system, shipped end to end. Onboarding plumbing, helpdesk, automation backbone, AI workflow, whatever's next. Scoped, delivered, documented, handed off.

Duration4 to 12 weeks
// 03 Embed

Fractional operator

Ongoing retainer, part-time. Embedded in your stand-ups, owning specific systems, acting as chief-of-staff for product or ops. When the team needs a builder consistently in the room.

DurationOngoing
// 05 Contact

If this sounds like what you need,
let's talk.

A 30-minute call is the fastest way to figure out if we're a fit. No deck, no pitch. Bring the mess.

Start a conversation