Real businesses. In their own words.
James and the follow-up that finally got done.
James Kuykendall is a construction business owner. In his Be Human interview, he describes an AI partner that helps with email, construction takeoffs and following up on contracts his office had not reached.
The operational problem
James’s account brings the focus to unfinished office work. Contract follow-up was one of the tasks he described alongside email and construction takeoffs.
These are distinct workflows. Following up on an existing contract is different from generating a new lead, and construction quantities still need an accountable person to review them. The interview should be read in that business context.
Where the AI partner helped
James describes support across email, takeoffs and contract follow-up. The story illustrates how an agent can fit around several recurring parts of an owner’s working day.
The public account does not document every integration, approval rule or technical step used in his environment. A new implementation needs its own workflow and access review.
What James reported
James reports recovering $10,000 in one week. This is his individual account in the interview, not independently audited accounting data or a guaranteed outcome.
The public story does not establish net profit, implementation cost or a repeatable weekly return. We keep that distinction visible so the reported recovery is not mistaken for a financial forecast.
A useful starting question
Which follow-up is waiting because someone has to find the context, prepare a message and keep track of the next step? Bring one example to the initial conversation with Be Human.
That gives the discussion a concrete starting point: the work to be completed, the person who reviews it and the outcome your team needs. Watch James’s original account below, then explore how managed implementation works.
