Why Codgent Exists

Most agencies put a senior engineer in the sales meeting, then staff your project with junior devs. We don't do that. The person you talk to is the person who builds your product. This keeps communication fast and quality consistent.

We're small by design. We take on two or three projects at a time so each one gets real attention. If we're full, we'll tell you, and we'll recommend someone else if we know a good fit.

What Kind of Work We Do

We build web applications, services, and backend systems. Most of our work is in Python and TypeScript, though we've shipped projects in Go, Rust, and Elixir when the problem called for it. We're comfortable across the stack but we're strongest on the backend and in the layer between systems: integrations, data pipelines, automation.

We don't take on projects where we're just extra hands following a Jira board. If you need someone to think through architecture, push back on bad ideas, and actually care whether the thing works in production six months later -- that's where we fit.

How We Work

We run projects in two-week cycles with a check-in at the end of each cycle. You'll see working code from week one, not mockups, not slide decks. We use Slack for day-to-day communication, Linear for tracking, and GitHub for everything else. Scope changes happen; we handle them with a quick conversation and a revised estimate, not a change-order process that takes a week.