IdeaFragmentsIdeaFragments
WorkProcess / How We WorkCapabilities01Custom software02AI / ML03Integrations04Analytics05Project supportAboutContact
Start a project →
About IdeaFragments

Hands-on.
Close to
the work.

What we believe

Software succeeds when teams stay aligned.

— 01 / Craft

The long middle is the work.

Most projects don’t fail at the start or the end. They fail in the middle, when assumptions break and decisions start to drift. That’s the part we focus on. Not just getting something started, or getting it over the line, but keeping it aligned while it’s being built.

— 02 / Ownership

Stay close to the work.

The person shaping the work stays responsible for building it. No layers, no handoffs that lose context.

— 03 / Honesty

Push back early.

If something doesn’t make sense, it gets called out before time and money are spent building the wrong thing. Clarity upfront makes sure what gets shipped still reflects why it was built in the first place.

— 04 / Tradeoffs

Make them explicit.

Every build runs into constraints. Scope, time, and cost will push against each other. The goal isn’t to avoid that tension, but to work through it and arrive at something valuable now, while setting up what comes next.

How we got here
2020 – present

From Getting It Built
To keeping it aligned.

2020

The first real product. Real users. Real problems.

CalendarSplice started as a simple integration problem, but quickly became the first product where people depended on the system day-to-day. Feature requests, bugs, edge cases, support questions, and operational issues turned building into something much more collaborative than expected. The best clients weren’t the ones with no problems. They were the ones who stayed engaged, asked questions early, and helped keep the work aligned with reality.

2021

The “why” matters more than the feature list.

While working with internal teams and client projects, it became obvious how quickly products drift when teams lose alignment on why something is being built in the first place. Features kept shipping, but customer needs and business direction slowly pulled apart. That tension shaped how projects are approached now: slow down upfront, pressure-test decisions early, and keep the build connected to the real problem all the way through implementation.

2022

From implementation to ownership.

The work shifted from simply building what was requested to helping shape what should actually be built. More time went into tradeoffs, sequencing, and reducing ambiguity before development started. Small, testable deliverables became the default, making it easier to catch misalignment early instead of discovering it months later.

Now

Hands-on. Close to the work.

Today, the focus is on a small number of projects that require real collaboration, clear thinking, and steady execution through the long middle of a build. Sometimes that means building independently. Sometimes it means pulling in trusted collaborators. Either way, the goal stays the same: keep the work aligned, grounded, and moving forward.

AI & Beyond

Useful AI over performative AI.

As AI became part of more products and workflows, the focus shifted away from novelty and toward usefulness. Early experiments explored how AI could behave proactively instead of sitting idle behind a prompt box waiting for user input.

At the same time, the rise of AI-generated code reinforced a core belief: every line of code is a liability. AI can accelerate development, but responsibility doesn’t disappear with generation speed. Production systems still require review, scrutiny, and human judgment.

The people

Small team. Direct communication.

Sam◆ It’s taught me....a certain respect for working with reality instead of against it
Architecture · System design

Sam

Engineer

I’m drawn to projects that start with a good question, not just a feature request. Most of the people I enjoy working with have ideas they care deeply about, but also the clarity to stay grounded in why those ideas matter in the first place.

Outside of work, I spend a lot of time gardening. Since 2018, that’s meant everything from herbs to broccoli to sweet potatoes, usually while competing with squirrels and other critters that seem just as invested in the harvest as I am. It’s taught me patience, attention, and a certain respect for working with reality instead of against it.

I’m also the father of a two-year-old, which has been its own ongoing lesson in adaptation. More than anything, it’s reinforced the idea that most people are just figuring things out as they go, even when they look like they have everything together.

Email
Depending on the project, we work with a small group of trusted collaborators across design and engineering. The work stays hands-on and close to implementation.
What We Use / The Stack

Preferences, not dogma.

Frontend
TypeScriptReactNext.jsTailwindStyled Components
Cross-platform, well-typed.
Backend
RailsNodeGo (standalone microservice)Python (standalone microservice)PostgresRedis
Rails or Node for web apps and APIs. Golang or Python smaller, single purpose, services
Mobile
IonicCapacitorReact Native
Capacitor lets you reuse the same Next.js codebase. React Native otherwise.
AI Workflows
OpenAIAnthropic
Infra
AWSDigital OceanCloudflare
[ Pull quote ]
Most projects don’t fail at the start or the end.They fail in the middle. That’s the whole difference.
— Sam, Engineer

Want to work
together?

Tell us what you're building. A paragraph is plenty. We'll get back within a business day with honest thoughts on scope, risk, and whether we're the right team for the job.

Start a project →