How we work · Build

We build with AI.

Working systems in Claude, built inside your business by people sitting with your team, and tested on your real work.

What we build

Custom connectors.A connector for a system that doesn't have one yet. The ones we've built and run are on Connectors.For Icelandic Glacial we built two, which put Vividly and Kuebix inside Claude for the finance and logistics teams.

Two Kuebix lookups through the custom connector, then Claude's answer.

Where's shipment SAMPLE-1042, and can you pull its bill of lading?

Kuebix · shipment lookup Kuebix · bill of lading

SAMPLE-1042 is in transit and on schedule.

Carrier
Example Freight Co.

Picked up
Warehouse A, Tuesday

Delivery
Customer DC, Thursday (estimated)

Bill of lading
BOL-000123, attached

Illustration with sample data. Kuebix has no off-the-shelf Claude connector, so we built one: read-only, for freight quotes, shipments, bills of lading and tracking.
Apps and tools.A working app where a manual routine is slowing the team down.For Lone Star Attorney Service, an onboarding app that files the paperwork and creates the ServeManager and Ramp records.
New application Example Process Serving LLC · Sam Sample Harris County · W-9 attached

Onboarding app
- Files the application and W-9Drive
- Logs the applicantTracking sheet
- Sends the welcome emailGmail
- Sends the Harris County Ramp instructionsGmail
- Alerts the intake mailboxGmail
- Creates the company recordServeManager
- Creates the vendor recordRamp
Left for the team: about a minute of review.
Illustration with sample data. What Lone Star's onboarding app does with each application, with no one copying between systems.

How a build runs

Scope it on the first call. One workflow or one team, and what "working" means for it, agreed before we build anything.
Start on site. We set up inside your own accounts with your IT, and watch the work before we build. At Lone Star the first day on site went to shadowing the team.
Build on your real inputs. Your documents, your data, your edge cases, in a handful of long working sessions with a short check-in each week, so you see it running well before it's finished.
Train your team before it goes live. Every build includes the training.
Keep building. The first system usually shows you the next one. We keep improving it with your team.

What Icelandic Glacial had running, month by month June to September 2026. Bars start in the order things began, spaced evenly within each month. Not to scale.

One company-wide Claude workspace, from June
NetSuite and Microsoft 365 connected, from June
Office hours open to finance, from June
Structured training under way, from July
Vividly connector live, from July
Kuebix connector live, from July
NetSuite accuracy skill on every seat, from August

By September 24 68 of 70 seats used in the 90 days 47 people using Claude every week July close run in Claude

From the Icelandic Glacial case study. Seat figures from its Claude admin analytics for the 90 days to September 24, 2026. Case study.

What "tested on your real work" means

Not sample data. At Icelandic Glacial, the Kuebix connector went live on July 31 for freight quotes, shipment lookups, bills of lading and tracking, and within a week the finance team was using it alongside NetSuite and Vividly. Lone Star's onboarding app went live in late June on real applications, and by mid-July Soha Jivani put her time per server at "a minute per job, max." If it doesn't hold up on your data, it isn't done.

What you hold

Terms for custom connectors and apps are set in the proposal. The skill libraries, prompt libraries and user guides that come with them are yours outright. Your team is trained on what we build before it goes live, and we keep building from there.