Skip to main content
Intempt

How we work

How we work

Intempt is structured for speed, autonomy, and innovation.

No big separate functions. No layers of communication. No complex approval chains. A single project team goes from idea to deploy independently. Read our Operational Principles and Work Principles for the philosophy behind this structure.

Sprints

We run 1-week sprints. A new sprint starts immediately after the previous one ends. Sprint planning happens with the Scrum Team and Product Owner at the start of each cycle. Sprint goals are published on the OKRs page.

Daily standups and check-ins

Every day starts with a standup and ends with a check-in. Three questions:

  • What did you do yesterday?
  • What will you do today?
  • What blockers do you have?

Backlog grooming happens regularly to make sure upcoming work is scoped, estimated, and ready to pick up.

Show & tell

End of each week. We celebrate sprint work. People talk about what shipped, problems they worked on, solutions they found. The team votes on a winner who takes home the Golden Mic for the week.

We write issues, not user stories

An issue only needs three things: title, team, and status. Break it down as small as possible. Assign it to a single owner.

Why not user stories? They add overhead without value. A roundabout way to describe tasks. Time-consuming to write. Complicated to scope. They don't match real conversations about what needs to get built.

Development flow

Every feature moves through 9 stages. Each stage has clear ownership and exit criteria. See our Engineering Principles for the technical standards behind each step.

  1. 1Plan & spec -- define scope, write specs (with AI), create mocks in Lovable or Figma. Agree on what and why before code starts.
  2. 2Groom & scope -- break it into issues, estimate effort, assign owners.
  3. 3Build -- backend first, then frontend on top. Claude Code and Cursor for implementation, AI-assisted code review. Nothing merges without review.
  4. 4Test -- API tests, QA automation, product owner tests the full flow end to end. If it breaks, it goes back.
  5. 5Ship & monitor -- push to production, run regressions, watch for issues.

🤖 AI is how we work

Every team member at Intempt works with AI agents daily. Not as a side experiment -- as the primary way work gets done. We use Claude Code with harness and loop engineering for backend services, Lovable for frontend prototyping and full builds, Claude on claude.ai for strategy, writing, analysis, and coworking sessions. Every person has AI agents running alongside them throughout the day.

  • Engineers run Claude Code with harness and loop engineering -- multi-agent workflows, automated code review, test generation
  • Product coworks with Claude on specs and prototypes in Lovable. Marketing uses AI for content, campaigns, and creative
  • Everyone uses claude.ai as a thinking partner. AI agents handle support, code review, docs, and deployment checks
If you are not comfortable working with AI tools daily, this is not the right place. We don't use AI occasionally -- it's woven into every process, every team, every day.

Every role builds

Marketing sources and closes deals -- there is no sales team, no SDR, no AE. Product writes specs engineers can build from without back-and-forth, prototypes in Lovable before engineering picks it up, and evaluates AI output quality across the product. Engineers own services end-to-end -- you built it, you monitor it, you fix it. Everyone uses AI tooling (Lovable, Claude Code, Cursor, claude.ai) to multiply their output. Nobody is just a coordinator.

Customer support is AI-first

First-line customer support is fully AI-driven via Plain. Blu Chat (our AI agent) resolves the majority of tickets autonomously from our docs across Slack, Discord, and email. Sales questions route to marketing. Product questions route to product. Confirmed bugs land in the engineering backlog. Nobody is stuck in a queue -- AI handles the queue.

On-call availability

On-call is opt-in and compensated. Team members who participate receive 15% of their daily rate per on-call day, plus incident-based multipliers for production issues. Rotation is weekly among those who opt in. No penalty for not participating -- teams coordinate coverage among themselves.

Customer support rotation

Engineering teams coordinate a weekly customer support rotation. The person on rotation triages customer-reported issues, works with the customer directly, and closes the loop. This keeps engineers close to real user problems instead of building in a vacuum.

Want to work at Intempt?
Check out our open positions
How We Work | Intempt Handbook