Skip to content

Speed needs safety and control.

This is how Lindy Logic is built so your team can move fast and still depend on the result.

A racing yacht heeled hard over in rough water, other boats behind it.

The assistant writes code for the hard parts.

When a question needs a sum, a lookup across tables or a file, the assistant does not answer from memory. It writes a short program, and the program runs on our servers.

Logic that holds
A program follows the same logic on each run. That is what makes a quote add up on Monday and again on Friday.
Less of your data sent away
The program reads your tables and files where they are stored. That reduces how much of your data has to be sent to the model provider.
Fewer turns
One program can search, read, calculate and write the file in a single run, where a chat would go back and forth. Fewer turns usually means a faster answer at lower cost.

It is not foolproof. A program can be wrong and a model can misread a question. Each run keeps a record of what it did, so a person can check it.

One script, every tool, one answer.

Most assistants call one tool at a time and think out loud in between. Ours writes a short Lua script that chains its tools in a single run: search, read the pages, file the rows in a table, do the arithmetic.

Fewer round trips
Often one run where a chat would take a dozen turns.
What the guide is allowed
The script can call the abilities switched on for that guide. Access rules stay in force underneath.
A new ability is a new function
Each ability we add appears on the same surface, ready to combine with the rest.
local hits = ai.search_topic.search({
  topic = "suppliers", query = "cargo bike brake pads"
})

local rows = {}
for _, hit in ipairs(hits) do
  local page = scraping.scraper.read_page({ url = hit.url })
  rows[#rows + 1] = { url = hit.url, price = page.price }
end

dyn_tables.table.import_csv({ table = "supplier_prices", rows = rows })

table.sort(rows, function(a, b) return a.price < b.price end)
return { cheapest = rows[1], with_vat = rows[1].price * 1.24 }
A sketch of one run: a search, page reads, a table, a sorted total with VAT.

What the assistant can reach.

The model does not answer from memory. It writes a short script that asks your sources, then replies with what they said.

A search topic, a scraper, tables and uploaded documents feed the model, which writes a script to ask them and answers the person. Search topic The web, or only vetted sites. Scraper Pages it reads into tables. Tables Price list, stock, FAQ, forms. Documents Specs, policies, guides. The model Picked per guide: OpenAI, Anthropic, Mistral or Google Gemini. Writes one Lua script that asks the sources it may use, does the arithmetic in code, and reports what it found. asks answer Your customer On your site, or on the guide's own page. No account needed unless you want one. Replies are marked as AI.

Swipe sideways to see the whole picture.

Switch on the abilities you need. Ask for the next one.

The platform is ours end to end, so a request does not join a queue behind a roadmap. It gets built, and every team's workspace gets more capable with it.

Search
The open web, or a search topic limited to sites you vetted, so the answer starts from the right place.
Scrape into tables
Fetch the supplier portal, the price list, the pages that change weekly, into a table the assistant can read.
Tables and forms
Your prices, stock or FAQ as tables the assistant reads and fills. Public forms collect rows; CSV moves them in and out.

Our servers do the hard work, not your device.

Lindy Logic runs in the browser you already have. The page stays light because the work happens on our side: the home page's own code, styles and fonts come to about 300 KB, less than one phone photo.

A phone is enough
Start a workflow, read a table or join a conversation from a phone. The hard tasks do not send you back to a desk.
Nothing to install
No app to download and no updates to keep up with. An older laptop is fine.
Easier on the battery
Your device shows the page. It does not run the model or crunch the data.

Structure, three ways.

A bigger model is not the fix. What makes the work dependable is the shape you give it.

Structured sources
A page you chose beats the whole internet. A table with columns beats a folder of PDFs.
Structured work
A job written as steps: a script computes, a template fills in the file, the assistant drafts where judgement is needed, a teammate approves. It runs when you ask, on a schedule, or when a file arrives.
Structured answers
A price, a date, a next step. Not a paragraph your customer reads twice and then rings you about.

One workspace, in the open.

Your team's home is a feed of conversations, so nobody works alone in a private chat.

Everyone in one conversation
Sales, support and the customer in the same chat with the assistant, in real time. Every conversation is a card in the feed, arriving as it happens.
Tables that fill themselves
Name the columns you want and point a scraper at the pages. Each page comes back as a row the assistant can read.
One name for one thing
The same customer spelled five ways in four systems becomes one name. The assistant proposes the matches by rules you set, and you approve them.

Three jobs it does better than a page.

We are always curious to hear the one you have in mind that is not on this list.

Customer support
Quotes, product advice, FAQs and order questions, answered without hopping through five pages.
Lead generation
Engage cold traffic, qualify the lead and book the meeting from the same conversation.
Document automation
Assemble the documents that eat an afternoon each: several sources combined and formatted, written as a file you can send.

Ready to accelerate with confidence?

Half an hour is usually enough to tell whether this is worth setting up for your team.