LongSpoke.

Business systems & software

Good technology.
Put to work.

You know your business. LongSpoke builds custom business software, connects your Microsoft 365 tools, and makes AI useful in everyday workflows. Clearly explained and built around your operation.

Try a sample workflow Why LongSpoke

Thoughtfully made. Clearly explained. Built to be useful.

A workflow, in outline
A document moves through rules and context checks. A person reviews when needed, and the work reaches a clear next step with the team kept informed.
Custom softwareConnected systemsBetter ways of working

01 — The purpose

You shouldn’t have to become a software expert to benefit from better software.

There is a gap between what technology can do and what a business can put to work. Finding the right tools, making them fit, and keeping everything moving can become a job of its own.

LongSpoke starts with your understanding of the operation. Together, we make the possibilities clear and build something useful, with the people doing the work involved along the way.

02 — See it in practice

Follow the work.
See what becomes possible.

A document arrives. The details are checked. Someone makes a decision. A useful result is prepared. Try the steps and see what happens underneath.

The working sample Synthetic · device-local

Follow the work.
Change the outcome.

Choose a document, change a value, and see what needs a person’s judgment. Then take away a useful packet.

No sign-in. No client data.
No emails or accounting writes.

5 examples to explore
LS-INV-1048

A supplier invoice, checked against what arrived

Reconcile a sample invoice, purchase order and receiving slip. Keep a quantity exception visible for review.

  1. Open source sampleComplete
  2. Check the working recordComplete
  3. 3
    Record the human decisionCurrent step
  4. 4
    Prepare the local packetNext
  5. 5
    Keep external actions separateHeld
01
Start with the source

Sample Supply Co. · synthetic · Invoice + receiving slip

Original sample document
FICTIONAL / FOR DEMONSTRATION
SYNTHETIC SAMPLE — not a real supplier document
Invoice SAMPLE-4831 | 2026-10-20 | Due 2026-11-19
Sample Supply Co. | Purchase order PO-1048
12 valve kits × USD 125.00 = USD 1,500.00
Purchase order: 12 units. Receiving slip: 10 units received.
No tax or freight in this simplified sample. Two units remain unreceived.
The original stays intact when you edit captured values.
Captured values
Try changing one
An actual calendar date from 2020-01-01 through 2035-12-31.
An actual calendar date from 2020-01-01 through 2035-12-31.
US dollars. This sample does not convert currencies.
US dollars. This sample does not convert currencies.

Deterministic sample rules. No live model reads this document. Use the supplied fictional records only.

02
Make the exception clear

Useful checks, with the evidence close by.

Ready for a human
6 passed2 need attention

1 exception needs a human decision before preparation.

Review source evidence, then approve preparation with a reason or return for correction.
Document
LS-INV-1048
Data
Synthetic sample only
Calculated invoice total
USD 1,500.00
Units awaiting receipt
2
Destination
review packet
Connection
Online · no external integration
See the checks & evidence8 rules
Required fields and bounded valuesPass

Required fields, dates, counts and amounts are within this sample’s supported bounds.

LS-INV-1048 · Working values are checked against the synthetic field definitions, not an external system.
Line total reconcilesPass

Quantity × unit price = USD 1,500.00; the entered invoice total is USD 1,500.00.

LS-INV-1048 · Invoiced quantity: source 12 units; evaluated 12 units | Price per unit: source USD 125.00; evaluated USD 125.00 | Invoice total: source USD 1,500.00; evaluated USD 1,500.00
Invoice matches received unitsAttention

2 invoiced units are not yet received in the working record. Record the reason or return for correction.

LS-INV-1048 · Invoiced quantity: source 12 units; evaluated 12 units | Received quantity: source 10 units; evaluated 10 units
Quantities stay within the orderPass

Compare both billed and received units with the order; overages require review.

LS-INV-1048 · Ordered quantity: source 12 units; evaluated 12 units | Received quantity: source 10 units; evaluated 10 units | Invoiced quantity: source 12 units; evaluated 12 units
Purchase order reference matchesPass

The original sample purchase order is PO-1048; a changed reference needs verification.

LS-INV-1048 · Purchase order: source PO-1048; evaluated PO-1048
Due date follows invoice datePass

30 calendar days between invoice and due dates, calculated in UTC.

LS-INV-1048 · Invoice date: source 2026-10-20; evaluated 2026-10-20 | Due date: source 2026-11-19; evaluated 2026-11-19
Terms fit the sample review windowPass

Terms longer than 90 calendar days require review in this sample.

LS-INV-1048 · Invoice date: source 2026-10-20; evaluated 2026-10-20 | Due date: source 2026-11-19; evaluated 2026-11-19
Human review recordedAttention

Choose approve for preparation or return, and record a reason of 8–500 characters. Nothing is automatically approved.

This records the decision supplied in this demo session. It is not authenticated identity, a second person's sign-off or authority to send/post.
How the decision travels
  1. Open source sample

    LS-INV-1048: a synthetic fixture, not a private upload or live OCR result.

  2. Check the working record

    Local deterministic rules evaluated the supplied fields. No model or external system was called.

  3. Record the human decision

    A reason is required. Role preview is not another person's approval.

  4. Prepare the local packet

    Resolve the review path before preparing an approved packet.

  5. Keep external actions separate

    Prepared for local download. No external action occurred.

03
Keep a person in the loop

A reasoned decision, not an invisible override.

A useful, portable record of the work. Approval applies to this destination; changing it requires a fresh review.

Preview only · no real user switch

The sample is captured. Open the reviewer’s view to record a decision about the exception.

04
Make the next step useful

A clean handoff, with the source, checks and review attached.

Selected destinationReview packet

Record a human review and note to unlock the downloadable packet.

Try a connection change
Connectivity scenario

Actual device signal: checking…. A browser’s network signal does not confirm a service connection. This sample calls no cloud AI or external destination.

Local history0

This device’s sample activity. It is not a shared or tamper-proof audit log.

Edit a sample or record a decision to see the sequence here.

Preparing device-local draft storage…

Ready for a human

A real, interactive example using fictional records and local rules. Prepared emails and accounting outputs are samples; nothing is sent or posted to an external system.

03 — Built around the job

The right shape
for your work.

01

Custom business software

A focused tool for the part of the business that needs it. The starting point is the job your people need to do.

02

Microsoft 365 integrations

Connect information and reduce awkward handoffs, including within Microsoft 365 and Power Platform environments.

03

AI & workflow automation

Put rules, useful AI and human review into a clear process. New capabilities are considered, tested and introduced when the benefit makes sense.

Explore the services and practical examples →

Some of the thinking underneath

Some jobs need a custom experience. Others need a better connection, a simpler process, or more from the tools already in place. The choice should serve the operation.

Desktop, mobile, Microsoft and offline needs are considered in scope. Local capture and drafts are different from live collaboration or an external write. The working example makes those boundaries visible.

Modern AI can help with parts of the work. Clear rules, human decisions and a record of what happened still matter. This public example uses deterministic rules; it does not call a live language model.

04 — A clear way forward

Small enough to understand.
Useful enough to matter.

Work moves in agreed phases. You can see it, try it, comment on it, and understand what comes next.

  1. 01

    Scope & schedule

    Understand the work, agree on a useful first phase, and make the scope and timing clear.

  2. 02

    A working sandbox

    See and try a working version before it becomes part of the day-to-day operation.

  3. 03

    Test & comment

    The people who know the work put it through its paces. Feedback stays close to what needs to change.

  4. 04

    Refine & accept

    Resolve the issues, test the changes, and agree when the phase is ready.

  5. 05

    Release & look ahead

    Put the accepted work into use, make the handoff clear, and decide what is worth improving next.

Keep the arrangement clear, too.

Work is typically month to month. Larger builds have an agreed scope and milestones. The next phase is a conversation, with the work and expectations made clear.

05 — The philosophy

The LongSpoke approach

Understand the work.
Make technology useful.
Keep it clear.

Good systems make the next step easier to understand. LongSpoke starts with the people doing the work, the decisions they need to make and the information they need to trust.

The useful technology belongs underneath a clear experience. People should be able to find the right record, understand what needs attention and see what happened without learning the machinery behind it.

Technology will keep changing. LongSpoke evaluates what becomes possible, tests worthwhile improvements and introduces them through an agreed scope. The system should have room to grow while the day-to-day work stays understandable.

A sensible place to start

Tell me about
the work.

A recurring frustration. A handoff that takes too long. An idea you haven’t been sure how to build. Start there.

Email LongSpokejustin@longspoke.com