Embedded engineering support

Add a second perspective to your production AI team.

A Webisoft engineer works inside your team to move higher-value work forward faster, while respecting the governance and access model you have already built.

Prepared for
Jason Kou, Jtech
Prepared by
Phil Therien, Webisoft
Date
November 13, 2026
Engagement
Monthly and adjustable

01 / Where your team is today

Production AI is already live. The constraint is capacity and perspective.

Your customer email and live-chat agents are live. A phone agent is in testing. A CLI layer lets agents act across your ERP, HubSpot, Zendesk, Shopify and Amazon Seller Central.

You have also built the governance most teams skip: a controlled plugin for Claude Code and OpenAI clients, with per-employee and per-group permissions, defined functions and job auditing. A custom harness keeps agents inside narrow boundaries instead of letting them write arbitrary scripts.

Most platform decisions now run through one internal point of view, and each failed task becomes a backend function someone builds by hand.

Your operating environment
ERPHubSpotZendeskShopifyAmazon Seller Central
Customer agentsEmail and live-chat agents are live. A phone agent is in testing.

02 / What we would work on

Four priorities, ordered by your team.

Choose a focus area to explore the problem, the work and the outcome.

01

Focus area

Keep the customer-service agent on task in long conversations.

Your agent loses the original request or diagnostic goal as exchanges get longer. We would check how history is passed to the model and write a compaction prompt that always preserves the initial question and core context.

Outcome

The agent holds the customer's goal from first message to resolution.

Alongside these, your engineer is a standing second opinion on architecture and implementation choices as they come up.

03 / How it works

Inside the team, not outside the workflow.

01

In Lark with your team

Your engineer joins your Lark workspace, takes part in your channels and answers questions as they come up, like any other team member.

02

Inside your access model

They work only in the repositories, systems and environments you grant. Anything that needs production access goes through your existing permissions.

03

Fast start

The first two weeks cover an architecture walkthrough, an agreed priority list and a first concrete deliverable on the top item.

04

Regular and adjustable

A monthly review covers progress, next priorities and whether the support level still fits. The engagement runs month to month.

Week 1Architecture walkthrough
Week 1Agreed priority list
Week 2First concrete deliverable
MonthlyProgress and priority review

04 / Support levels

Choose the capacity that fits the current priority.

Three monthly levels, all in USD. Each level can change as your needs change.

Advisory

$5,000 / month

Regular working sessions plus ongoing support in Lark.

Best forArchitecture reviews and a second opinion on key decisions.

Part-time

$8,000 / month

A consistent engineer working part-time on agreed priorities.

Best forSteady progress on one or two focus areas.

Dedicated

$13,000 / month

A full-time engineer fully embedded in your team.

Best forMoving several focus areas at once, including the phone agent launch.

05 / Why Webisoft

We build the same kind of system you are building, for multiple companies at once.

01

Governed agents are our daily work

Portal, our AI automation platform, runs on predefined capabilities, granular permissions, auditing and isolated per-request execution.

02

Model-agnostic experience

We build across Claude and OpenAI models, including MCP connectivity, so recommendations are not tied to one vendor.

03

Production, not demos

Our value is in what comes after the demo: security, compliance, deployment, upgrades and maintenance.

04

Deep systems integration

Our team of about 40 engineers does custom development, ERP implementation and AI integration across the business systems your agents already touch.

06 / Next steps

Choose the right starting level.

Portal documentation is coming separately, so you can compare it with your internal platform on its own terms.

  1. 01Share this proposal with your leadership.
  2. 02Walk through questions and select the right level.
  3. 03Agree the first priorities and bring your engineer into Lark to start onboarding.

Phil Therien

Partner and Chief Revenue Officer, Webisoft