AI implementation for business operations

The workflow your client still runs in Excel. We build the software to fix it.

Your client’s team still spends the week exporting, reconciling, re-keying, emailing for approval, rebuilding the same report and chasing the owner of a number.

AI looks easy to try. Making it useful inside a large company is the hard part. Show us the workflow. We build the software around the systems they already run.

The work your client still does by hand.

The big systems hold the records. The work between them lives in spreadsheets and inboxes.

Someone on your client’s team carries it every week.

  • A reconciliation rebuilt every monthAn analyst exports two reports and matches them line by line in Excel.
  • A tracker three teams update by handEach team keeps its own copy. Nobody knows which one is current.
  • An approval that lives in emailThe request sits in an inbox. Nobody can see who holds it or for how long.
  • A weekly report built from exportsSomeone pulls numbers from three systems and pastes them into a deck.
  • A deadline watch in one person’s headThe dates sit in a spreadsheet. One person remembers which ones matter.
  • Requests re-keyed from emailRequests arrive in every shape. A coordinator types each one into the system of record.

We replace that step with software.

We connect to SAP, Salesforce, Workday, Excel and the rest where the client grants access and the system allows it. We do not replace them.

Operations data only. We never ask for patient records.

Software that fits the systems they already run.

Your client’s team does not want another system to learn. We build the missing step and leave the rest in place.

We learn how the workflow runs today. We redesign it. Then we connect the tools the team already uses and build the software that is missing.

A build uses only the parts the workflow needs.

  • ConnectionMoves data between the systems the team already uses.
  • RuleApplies a business rule the same way every time.
  • Scheduled checkReads a system or an outside source on a timetable.
  • DataKeeps one record of each item and where it stands.
  • ViewShows a manager what needs attention.
  • AlertTells the right person when an item needs them.
  • AI stepReads messy text or drafts words. Used only where plain software cannot do the step.

We use AI where it makes sense.

We use normal software where normal software makes sense.

We care about the business result.

A build with no AI step is a normal result.

Four example builds

Each card is an example of what 3Fold can build. None describes a client project.

ExampleNo AI step in this build

The monthly reconciliation

Two exports and a day of matching by hand every month.

  1. CheckA scheduled check reads both exports each night.
  2. RuleRules match the lines that agree.
  3. ViewA view lists only the lines that do not match.
  4. PersonThe analyst clears each exception.

ExampleNo AI step in this build

The approval in email

A request waits in an inbox until someone chases it.

  1. ConnectsAn integration collects each request from email and the request form.
  2. RuleA rule sends a request up a level when it waits past your limit.
  3. ViewOne view shows every open request and who holds it.
  4. PersonThe approver still makes every decision.

Example

Requests re-keyed by hand

A coordinator retypes each emailed request into the system of record.

  1. ConnectsAn integration collects every request in one queue.
  2. AI stepA model reads each message and fills in the fields.
  3. RuleA rule flags any request with a missing field.
  4. PersonThe coordinator checks each one before it goes in.

Example

The weekly report

Someone rebuilds the same deck from three exports every week.

  1. ConnectsIntegrations read the numbers from each system.
  2. ViewOne view shows them side by side.
  3. AI stepA model drafts a plain summary of what changed.
  4. PersonA manager checks it before it goes out.

How we work with a consulting team.

On your client project

3Fold as your build partner

You need someone who takes the Excel work off the project and hands back working software.

  • You keep the client relationship.
  • We scope every build in writing. You can forward the scope as it is.
  • Fixed price per build. A standard build is $5,000.
  • We deliver inside your engagement or straight to the client. The client chooses.
  • Every build ends with documentation and a handoff to the person who will own it.
  • No retainer. Later work is quoted in writing and priced on its own.

Start from the written intake or send your own write-up to kent@3fold.me.

Too small for your firm

Send it to us

You need a place to send client work that is too small for your firm.

  • Send the client to 3fold.me/start or forward this page.
  • The client describes the workflow in writing and gets a written scope.
  • The client buys in writing. Nobody has to meet.

Download the one pager (PDF)

A fixed price you can quote.

A standard build covers one workflow and up to two or three of the client’s systems.

$5,000

Standard build

One time. No subscription. No sales call.

To start

$2,500

Paid after you approve the scope and sign the agreement.

At acceptance

$2,500

Due when the build is ready for acceptance.

What a standard build covers

  • One workflow, mapped and redesigned
  • Up to two or three existing systems
  • The integrations that are technically reasonable
  • Rules and scheduled checks
  • A view or alerts where they help
  • Testing and deployment
  • Documentation and handoff

For your first standard 3Fold build. Larger or additional builds are scoped separately.

Security and data.

Your client’s security team will ask where the data goes and who approves what leaves.

  • AccessWe ask only for the access the build needs. Read only wherever the tool allows it. The client can take that access away at any time.
  • StorageData is encrypted in transit and at rest. Files sit in private storage and open only by signed link.
  • Server sideModel requests run on our server and never in a browser. Intake and project records sit behind row level security.
  • The modelA language model provider reads what you write in the intake and any data you connect. Today that provider is Anthropic. We never use your data to train anything.
  • A person approvesA person reviews every message before it goes to anyone outside your team unless your written scope says otherwise.
  • What we never takeCard details go to Stripe. We never see a card number. The project page never asks for a password or a key.

Who you put in front of your client.

You carry the risk of whoever you bring in. At 3Fold that is one person.

Kent Shi

Founder of 3Fold. Harvard Kennedy School ’22.

  • He scopes and builds every 3Fold project.
  • You work with him directly.
  • Questions go to kent@3fold.me.

Three products 3Fold built. Each one is live.

One client case

A Shopify e-commerce agency coordinated time-sensitive client launches in Basecamp.

3Fold built an operating layer that surfaces what needs attention, flags work at risk and prepares follow-ups while the account manager stays in control.

The agency stays unnamed. We name no client without written permission.

Two ways to start.

Send us the workflow

Describe it in a few written lines and answer the follow-up questions. You get a written scope within two working days.

Your own write-up works too. Send it to kent@3fold.me.

Forward this page

Send the link to the client or to your team. The one pager tells the same story on one page.

Questions

Can you work under our firm’s contract?

Our standard terms are at 3fold.me/terms. Ask us in writing about your firm’s own contract.

Who owns the code?

When the final payment clears you own the custom code we wrote for you and the documentation that goes with it. Software and services from other companies keep their own licenses and terms. Your data is always yours.

Do you sign an NDA?

Our terms already cover confidentiality. What we learn about your business while doing this work stays between us. We use it only to do the work. Ask us in writing about a separate NDA.

Can you build for a regulated client?

Yes for operations work. A request that touches health data or unusual security needs gets a written scope review before any payment.

How fast does a scope come back?

You get a written scope within two working days of a finished intake. A request that needs a closer look gets a written answer instead.

What if the work is bigger than one workflow?

Each workflow gets its own written scope and price. Larger or additional builds are scoped separately. Nothing outside the agreed scope starts without a yes in writing.