top of page

AI FIELD NOTES

OUR LIVING AI ENGINEERING LIBRARY 

If you want to understand how we think,
 

ai-hero2.png

build, and use AI, this is the source.

How we work with AI

AI isn’t something we sprinkle on top of projects at Bobcats Coding. It’s how we work.  

We’ve deliberately built AI into our delivery system: how we specify, how we build, how we test, and how we learn. So when you work with us, you're not just getting an AI-capable team, but a team whose internal mechanics are fundamentally different. And that difference shows up in speed, clarity, and reliability.

 

That matters because about 90% of our work comes from US-based teams who need shipping momentum they can actually trust.

 

In our experience, every time the industry moves into a new era, like cloud, mobile, DevOps, or modern frontend stacks, the teams who keep winning aren’t the ones who chase every new tool. They’re the ones who adapt their delivery mechanics fast enough to turn the shift into an advantage. AI is this kind of shift.

We built Bobcats to be that team: engineering partners who stay current, adapt fast, ship reliably, and treat your product like it’s ours to make it succeed.

HOW WE USE AI?

We still believe great product work comes down to a simple loop: Specify → Build → Analyze → Repeat.​

What's changed is that AI rewired the economics inside that loop. 

We don’t even have to go back that far to a time when Build was the most expensive part of product development, sometimes by an order of magnitude. It cost 10x more than Specify or Analyze, so teams front-loaded everything into requirements. In the AI era, Build doesn’t have to be the bottleneck anymore. Execution can be dramatically streamlined and faster, which means we can ship more iterations, learn sooner, and de-risk the product through real usage.

That shift is what’s changing how we deliver at Bobcats Coding. Our priority is to optimize Build, so we can ship more iterations faster, with less risk. We invest in AI-assisted workflows and modern toolchains that speed up delivery without compromising production quality. And we adapt Specify and Analyze to match that pace, so every cycle feeds directly into the next.

OUR AI FIELD NOTES

Our AI Field Notes

Over the past few months, our engineers have been building a living internal library of the tools, processes, and workflows we use to keep that loop running faster in the AI era. We’re now open-sourcing it as our AI Field Notes. Unlike a static “best practices” page, it keeps growing from our recent client projects, internal experiments, and conversations with experts and clients day by day.

 

Inside you'll find:

DATABASE OF CASE STUDIES 

A central collection of real-world case studies from client and internal projects that also serves as our engineers’ written internal knowledge base.

Irodai-bg14_k_edited_edited.jpg

WORKFLOW EXPERIMENTS BOARD

It’s a living board of AI-assisted workflows we’ve tested in real projects. Each experiment is tied to active case studies and positioned by how reliable it is and how deeply it’s embedded in our day-to-day work, from early exploration to production-ready practice.

ai field notes-bc01_k_edited.jpg

CASE STUDIES ORGANIZED BY PRODUCT ACTIVITES

This view organizes case studies by the core activities software teams perform, such as writing PRDs, prototyping, testing, deployment, etc. It helps you quickly explore the AI approaches we use for each specific product activity.

Irodai-bg38_k_edited.jpg

We're not making this public to impress anyone, but rather to be useful. This is our way of being transparent about how we work and making our delivery system easier to understand, adopt, and trust.

ai-hero-bg2.png

EXPLORE AI FIELD NOTES

OUR LIVING AI ENGINEERING LIBRARY 

READY TO MOVE FROM COOL
AI DEMOS 
TO REAL PRODUCTS? 

LET'S TALK!

We’ve got your message and will be in touch shortly.
Excited to learn more about what you’re building.🚀

bottom of page