Apexloop has its own MCP server. We walk through one concrete example of how an AI agent connects to your workspace, what it can read, how it proposes a change, and why writing always waits for your approval.
MCP is an open protocol that gives AI assistants access to data in business systems - without a manual integration for every tool. We explain how it works and why most business software will run on it within a few years.
The US government ordered Anthropic to suspend access to Claude Fable 5 and Mythos 5 models just three days after their launch. What this incident means for companies building agentic AI into their key processes.
Anthropic announced new models Claude Fable 5 and Claude Mythos 5. Fable 5 is designed for general use, Mythos 5 uses the same underlying model with relaxed constraints and remains
An off-the-shelf template is faster, cheaper and perfectly sufficient for plenty of companies. For others it's the start of two years of frustration. Three questions that reliably tell the two apart, and what to do with the answer.
One concrete flow end to end: an ordinary enquiry arrives, the system pulls out the line items and the company ID, fills in the company from the public registry, creates the job and stops at human approval. What you need for it, and where its limits are.
Three concrete edits that mean a support ticket and a wait in an off-the-shelf CRM: adding a custom field, reordering the sales stages and hiding prices from part of the team. Here's what they look like when they're settings.
No talk of transformation or productivity. Five concrete tasks you can hand to AI in a business system this week, three where a human should have the last word, and one rule that holds it all together.
A quote, a client list, a payroll table - every day someone on the team drops something like that into an AI tool. Three places that data can end up, and nine questions worth asking a supplier before an incident rather than after one.
Connectors haven't died and won't. But most of the scenarios companies build in them exist only because their tools can't talk to each other. When a connector earns its place, when it's a plaster, and what happens if you remove the cause.
Everyone knows the revenue on a project. Very few know the margin - because the hours logged and the amount invoiced live in different tools. How to join two numbers you already have, and why the result unsettles most firms.
Nobody consciously chose three systems. They accumulated - each one solved a problem and added a new one. How the typical software stack comes about, where context leaks out of it, and what can be done without a big bang.
Email opens aren't actually measured - what gets measured is an invisible image loading. We explain, without unnecessary technicality, why today's open-rate number is inflated and which metric holds up in its place.
A six-person installation company and four spreadsheets. A model walkthrough of one afternoon: what to put in the prompt, what comes out by itself, what needs adjusting by hand, and what actually changes in the first month.
Documentation, data and communication usually live in three different tools that know nothing about each other. Here's what a workspace looks like when they're connected and share the same context.
Ask what a custom app costs and every supplier answers the same way: it depends. Here's a concrete range for three routes to a business system, what the price is made of, and why it's decided by the three-year total rather than the first invoice.
Task tools are excellent at what they do - they hold a list of work. What they can't answer is who that work is for, what it cost and what comes next. Five questions your task manager can't answer, and what to do about it.
An off-the-shelf CRM is designed for the middle of the market. Your company isn't the middle - so half the modules stay unopened and the things that really matter live in a spreadsheet on the side. How to tell you're paying twice.
Three terms that get mixed up often, but describe different points on the axis between "no code" and "code the AI writes for you." We compare low-code, no-code and vibe coding on concrete criteria.
Writing software was always the cheap part. AI made exactly that part cheaper and left the expensive part untouched. What happens to a generated app over its first year in production, and how to work out in advance who carries it.
Excel for numbers, WhatsApp for quick agreements, email for orders, Zapier to connect them, a separate app for invoicing. We calculated what that kind of split actually costs a company.
AI app builders now turn a single sentence into a usable screen in minutes. What they don't do is everything else - the data, the permissions and the running of it. Here's exactly where the line falls between a prototype and a system your company actually runs on.
Excel is a great tool - until more than one person starts working on the same file. Here are the concrete signals that a spreadsheet has stopped being enough, and exactly what a database app solves differently.
Donors, grants, and financial reporting scattered across spreadsheets and emails are the rule rather than the exception at nonprofits. Here's how to build connected records without a dev team and without a big budget.
A paid helpdesk tool on top of the system a company already has means another account, more login credentials, and another place where context gets lost. Here's how to build a helpdesk directly on top of your own database.
Big CRM systems assume a sales department that a tradesperson or small service business doesn't have. Here's what to actually focus on when choosing a CRM for field work.
No-code means building software from ready-made, visual blocks instead of writing code. We explain how it works under the hood, through the four layers that make up practically every no-code application.
A company's name, address and tax ID already exist in the Czech public registry ARES. Here's how to have them filled in automatically instead of retyping them by hand for every new contact.
You hear 'AI agent' everywhere today, but few people say exactly what that means for company data. We break down what such an agent can really do - and where it should always stop and ask for your permission.
How to design databases, relations, formulas and views in Apexloop so the workspace can handle CRM, projects, invoices and internal processes without dead ends.
A page in Apexloop is not just text. It can contain databases, dashboards, media, QR codes, buttons, shortcuts, print templates and email content.
How to design node-based automations in Apexloop so they are readable, safe and useful for everyday team work.
Rollups in Apexloop are built from relations, filtered view columns and formula cascades. This lets you calculate project or company status from the lowest level of data.
Communication in Apexloop doesn't happen alongside work. Forms create records, emails are mapped to databases, attachments belong in file columns and chat stays with the page or record.
How to create PDF invoices, proposals, protocols, reports and newsletters from Apexloop databases, document pages, placeholders, QR codes and automations.
