peashoot
Start a projectMenu
peashoot

Write to us

brendan@peashoot.io

We build full-stack software

Websites, internal tools, integrations, and full products

Start a project See what we build
  1. 01InterfaceWebsites, products, and portals. The part everyone sees.
  2. 02Automation & AIAgents and workflows that take on repetitive work, with people at the checkpoints.
  3. 03IntegrationsCRMs, payments, ERPs, calendars, and the APIs in between.
  4. 04DataOne reliable record of what is actually happening.
  5. 05InfrastructureHosting, queues, monitoring. Boring on purpose.

Most websites stop at the surface. We build all the way down.

Two ways in

Two kinds of teams call us.

Some are engineering organizations putting AI to work in how they build. Others are businesses that need a better website and the systems behind it. Same team, same standard, different problems.

For engineering teams

Make AI a dependable part of how you ship.

You already build software. You want agents in the workflow without losing quality, and you need people who can work inside a real codebase.

  • Agent systems
  • Evaluation
  • Developer tooling
  • Infrastructure

For businesses

Start with the website. Fix what’s behind it.

You need a site that earns its keep, and you suspect the real problem is everything after the click: manual follow-ups, disconnected tools, the spreadsheet holding it all together.

  • Websites
  • Integrations
  • Internal tools
  • Automation

01For engineering teams

Engineering teams

The model is the easy part.

Useful output depends on the system around it: what context an agent sees, the workflow it follows, the checks it has to pass, and what each run costs. We design, build, and measure that system with your engineers, inside your stack.

run / add-rate-limit-to-exportIllustrativeReady for review
  1. task.received
  2. context.assemblescopedscoped
  3. repo.map
  4. team.conventions
  5. agent.plan
  6. agent.implement
  7. checks.run2 failing2 failing
  8. agent.repair
  9. checks.runpassingpassing
  10. eval.comparevs baselinevs baseline
  11. review.humanapprovedapproved
  12. change.ready

Context packet

  • Task scope
  • Relevant files
  • Team conventions
  • Acceptance checks

Checks

  • Unit & contract tests
  • Type and lint gates
  • Eval against baseline

Handoff

  • Review by the owning team
  • Deploy stays manual
  • Run trace kept for audit
Illustrative agent run. The context, checks, repair loop, and human checkpoint are the parts we engineer.
  • 01

    AI engineering workflows

    Context, task boundaries, and checks that make coding agents dependable on real work.

  • 02

    Agent systems

    Tool-using agents with guardrails, recovery paths, and people at the right checkpoints.

  • 03

    Evaluation systems

    Representative task sets and harnesses that show whether a change actually helped.

  • 04

    Developer tooling

    CLIs, bots, and internal platforms that take friction out of shipping.

  • 05

    Internal automation

    Pipelines for the repetitive work that keeps landing on engineers.

  • 06

    Custom software

    Production services and applications, built to your architecture and standards.

  • 07

    Integrations

    Dependable connections between your product and the services it relies on.

  • 08

    Systems design

    Architecture, infrastructure, and observability for the next stage of scale.

Agents, evaluation, developer tooling, and the infrastructure under them.

Explore engineering

02For businesses

Businesses

The website, and everything behind it.

Most companies come to us for a better website. The bigger win is usually what happens after someone clicks: the reply, the quote, the booking, the handoff, the spreadsheet nobody trusts.

  1. 01 Finds you

    A fast site that says the right thing

    • Search & analytics
    • Content system
  2. 02 Asks

    A clear inquiry or quote form

    • CRM record
    • Routing & alerts
  3. 03 Hears back

    A quick, specific reply

    • AI draft
    • Human approval
  4. 04 Books or buys

    Checkout or booking in a few taps

    • Payments
    • Calendar & inventory sync
  5. 05 Comes back

    A timely follow-up

    • Reminders & reviews
    • Reporting
A customer journey, above and below the line of visibility. Every stage has a visible moment and the systems that make it work.
01

Websites & digital experiences

Sites, booking and quoting flows, and customer portals that look exceptional and make the next step obvious.

  • Marketing sites
  • Booking & quoting flows
  • Customer portals
  • Design systems
02

Systems & integrations

Connect the site to your CRM, calendar, payments, and inventory so information is entered once and stays right.

  • CRM & ERP integrations
  • Payments & scheduling
  • Internal tools & dashboards
  • Data clean-up & migration
03

AI & automation

Automate follow-ups, triage, quotes, and reporting. AI where it saves real time, with a person approving what matters.

  • Lead triage & routing
  • Support drafts & answers
  • Quotes & documents
  • Reporting & alerts

Websites, the systems behind them, and the work in between.

Explore business

03How we work

Start with one real problem. Then expand.

Every engagement starts with something concrete: a workflow that is slow, a system that is unreliable, a website that is not pulling its weight. We fix that first, prove it, and earn the next step.

  1. Find the bottleneck.

    We map the workflow, the systems, and the people around it, then agree on what better looks like and how we will know.

    You getA focused plan and a baseline.

  2. Build the real thing.

    Working software in your environment, built alongside your team. Not a slide deck, and not a prototype that never leaves staging.

    You getCode, configuration, and integrations.

  3. Prove it. Hand it over.

    We compare against the baseline, document the tradeoffs, and leave you with something your team can run and extend.

    You getEvidence, documentation, and a clear next decision.

Built around your stack.

We work in your repositories, tools, and constraints. There is no platform to buy.

Evidence before expansion.

Each change is measured against a baseline before the next one is worth funding.

People stay in control.

Automation proposes. Your people approve what matters.

The man behind Peashoot

Brendan Duhamel

Software entrepreneur who has built and operated technology businesses internationally.

Write to Brendan

04Proof

Proof, with permission.

We publish client names, case studies, and results only with written sign-off. Until then, the best evidence is a conversation about your problem.

  1. 01

    Named with sign-off.

    Client names and logos appear only after written approval.

  2. 02

    Figures they agree with.

    Results are published only when the client confirms them.

  3. 03

    Never borrowed.

    Prospects, pitches, and demos are never shown as client work.

Want to see work relevant to your problem? Ask, and we will share what our agreements allow.

Ask about relevant work

Start a project

Tell us what’s slow, manual, or ugly.

Bring the workflow, the website, or the system everyone works around. We will tell you plainly what we would build, and whether it is worth building.

Engineering teamsAgents, evaluation, tooling, infrastructureEmail us BusinessesWebsites, systems, automationEmail us

Or write directly