Skip to content
Stone Solutions

What we do

Five kinds of work, and what each one looks like built.

The tools differ from one company to the next. The work underneath rarely does. Here is what each of the five looks like once it runs as a system, drawn from the projects that shaped them.

01

Enquiries, follow-up and partners

The situation

Leads, partners and clients are spread across mailboxes and lists. Whether a conversation gets a follow-up depends on who remembers it. Partners send deals in loose messages, and renewals arrive as a surprise.

What gets built

  • One CRM with a pipeline for each kind of opportunity: new partners, direct sales, partner deals, renewals. Existing contacts are moved in once.
  • A daily overview of open tasks, stalled opportunities and appointments, sent every working day.
  • Follow-up tasks that appear by themselves when a contact goes quiet, each with a draft message ready to send.
  • One form for partners to register a deal or request a licence, landing straight in the CRM with a confirmation back to the partner.
  • A renewal date on every licence, and a task well ahead of it.

What changes

You see at any moment which partners, deals and renewals are running, without searching a mailbox. Follow-up happens on time in busy weeks too, and growth rests less on the memory of the people at the top.

02

Quotes, files and onboarding

The situation

The same client information is typed into a quote, then a contract, then a file, then an onboarding form. In a busy week one of those steps is skipped, and that is the one that costs money later.

What gets built

  • Proposals and agreements assembled from the notes of one call and the data your CRM already holds, sent for signature from one link.
  • An intake form that prepares a new client's set-up, documents and accounts, so a team member checks the result instead of building it by hand.
  • Recurring files, letters and standard documents built from fixed templates and the data you already hold, and kept current.
  • A signed agreement that sets the next steps off by itself: the deposit, its invoice, the start of the timeline.

What changes

Every document is right the first time because it is built from one source, and nobody types the same information three times. The step that used to be skipped simply happens.

03

Reporting and data between systems

The situation

The CRM, the accounting package and the industry software each hold part of the truth. Somebody copies figures between them on a fixed rhythm, and the monthly overview is rebuilt by hand from spreadsheets and email.

What gets built

  • Data that moves between systems on its own, so a customer, an invoice or a project exists once and is the same everywhere.
  • Periodic reports and a dashboard of the figures you steer on, compiled automatically from the systems that hold them.
  • Incoming documents and emails read, sorted and entered into the right system, with only the exceptions reaching a person.

What changes

One source of truth instead of three versions of the same number, and an overview that is current whenever you open it. Data entry that used to take an analyst hours takes minutes, with someone checking rather than typing.

04

Content and letters from your own knowledge

The situation

Articles, newsletters and standard correspondence never get written, because the people who know the subject have no time to write. Off-the-shelf AI tools produce generic text that sounds cheap, and a wrong figure in print costs trust with exactly the people you want to convince.

What gets built

  • A knowledge base in a spreadsheet you control: the topics, what the company knows, the tone, and the facts that may and may not be stated.
  • A photo library built from your own website, described and tagged, so every piece opens with a real image from your portfolio.
  • Research per topic: the top search results and additional sources, summarised into a brief and an outline.
  • A writing step that follows the outline and your tone rules, and a separate editorial step that checks every figure and claim against the knowledge base.
  • The finished draft placed in your website's editor on a fixed day, with image, table of contents, reading time and search fields, and a notification by email.

What changes

A steady stream of pieces that sound like you and say only what you know to be true. You choose the topics, the knowledge base decides what is said, and nothing goes live without your approval.

05

Choosing the tool, and getting it used

The situation

Software has been bought and is barely used, several tools overlap, or nobody is sure which product to choose. Sometimes the work is still done by hand only because nobody had the time to set up the thing that would do it.

What gets built

  • An overview of the software you run, where it overlaps and where it sits unused.
  • The selection and roll-out of a standard product where that works better than a custom build, with the team set up on it and shown how it works.
  • A shared workspace and clear working agreements for AI instead of everyone on a personal account, with hands-on training per team.
  • Procedures and know-how captured and made searchable, so colleagues get an answer without interrupting the same person again.

What changes

The tool that fits, actually in use. Sometimes that is the whole job: the shareholder meeting of a company with around thirty shareholders in several countries moved from paper to digital registration, resolutions and voting with an existing product and no automation at all.

How the tools are chosen

Automations are built on n8n, an open workflow platform that can run in your own account and that your team can look inside. Where a good product already exists, it is chosen over a custom build. AI is used where it earns its place, with a check against your own knowledge and your approval before anything goes out, and never as the starting point. Third-party licences are billed to you directly by the provider, not through us.

Is your week in here somewhere?

Book the call
Book a call