Portfolio01–03

What we have built,
and what we build with.

Three engagements, and the parts they are made of. Figures are published as they are verified.


Clients

01–03
  • GTV Global
    Ongoing
    GTV Global

    GTV Global

    Revenue Orchestration System

    Before

    Finding and qualifying buyers was manual: building the list, checking each company against what GTV actually wanted, and writing the outreach one company at a time.

    What we built

    A custom sales and lead generation CRM, built around GTV's own buyer profile rather than configured from a template. It defines who is worth contacting, finds those companies, qualifies them against GTV's criteria, discards the ones that fail, and prepares personalised outreach for the ones that pass. A person approves before anything is sent.

    Working with the platform drastically reduced the manual time our team spent searching for leads, allowing us to focus on direct outreach. What stood out most was the high degree of personalization tailored to our specific preferences, alongside precise segmentation of our target clients. Additionally, the team was incredibly supportive throughout the entire process, providing hands-on assistance whenever needed. It proved to be an efficient tool for streamlining our audience targeting and outreach setup.

    GTV Global

    B2B services

  • Myne & Co.
    Delivered
    Myne & Co.

    Myne & Co.

    Lead generation and outreach system

    Before

    Reaching the right clients meant first knowing which ones were worth reaching, and there was no definition specific enough for anything to act on at scale.

    What we built

    It started with the ideal customer profile: what Myne's best clients had in common, made specific enough for a machine to apply. Then intent-based discovery, per-lead research delivered into the platform their team already works in, and an outreach strategy built on what the research surfaced.

    We knew roughly who we should be reaching, but not how to find them at any useful scale. SKAIYON started by working out what our best clients actually had in common, then built the system to go and find more of them.

    The part that changed how we work day to day is the research attached to each lead. Our team opens a record and already knows why this company is worth a conversation and what to open with. That used to be half an hour of someone's morning, per lead.

    Our lead volume is several times what it was. The more useful change is where the time goes: we spend it on outreach now, not on looking.

    Myne & Co.

    Design studio

  • Studio Hika
    Delivered
    Studio Hika

    Studio Hika

    Lead generation and internal automation

    Before

    The same problem as Myne to begin with, and then a second one: the parts of the studio's own process that were quietly taking the most time.

    What we built

    The same foundation as Myne: an ideal customer profile, intent-based discovery, and per-lead research delivered into their own platform. Extended from there into their operations, with custom AI tooling for the parts of the process consuming the most time, and their team trained on what was built so they can operate and extend it themselves.

    We came to SKAIYON to automate our lead generation and scale our outreach, and ended up rethinking how a fair amount of our work gets done.

    They started with who we should be talking to and why. Not a list, an actual definition we could act on, then built the finding and research around it. From there it moved into the rest of the business, automating the parts of our process that were quietly taking the most time.

    What I had not expected was how much of the value was in understanding. They explained what these tools do and do not do, so my team can use and extend them rather than depending on someone else every time something needs changing. The work is getting done faster, and it is less tedious than it was.

    Studio Hika

    Creative studio


Functions we build

01–16

The unit of work. One defined job, done the same way every time, on your data and your rules. Every one of these is built to order.

01 of 02
Function 01 of 16

Lead researcher

Builds the picture of an account before anyone speaks to it: who they are, what changed recently, and why now might be the moment.

Takes in
A company name, a domain, or a list of either.
Gives back
A brief on the account, and the reason it is worth a conversation.
  • Lead researcher: Builds the picture of an account before anyone speaks to it: who they are, what changed recently, and why now might be the moment. Takes in: A company name, a domain, or a list of either. Gives back: A brief on the account, and the reason it is worth a conversation.
  • Enquiry reader: Turns an inbound message, a form or a transcript into the structured fields the next step needs, with the original kept alongside. Takes in: An email, a form submission, or a call transcript. Gives back: The same enquiry as structured fields, original attached.
  • Qualifier: Scores against your criteria and routes what passes to the right person, with the reasoning attached so a decision can be checked. Takes in: A lead or an enquiry, and the criteria you actually use. Gives back: A score, a routing decision, and the reasoning behind both.
  • Follow-up manager: Runs the sequence nobody gets round to, stops the moment a human replies, and escalates anything that reads as a real conversation. Takes in: An open conversation and the sequence you want run on it. Gives back: Messages sent on schedule, stopped the moment a person replies.
  • Quote preparer: Assembles a draft from your pricing rules so the person quoting is editing rather than starting from nothing. Takes in: A scoped request and your pricing rules. Gives back: A draft quote to edit, rather than a blank document.
  • Report builder: Compiles the recurring report from the systems it already lives in, on a schedule, so nobody assembles it by hand. Takes in: Read access to the systems the numbers already live in. Gives back: The finished report, on the schedule you set.
  • Listing writer: Rewrites and adapts the same listing per channel, keeping the facts identical and the phrasing appropriate to each. Takes in: One listing, and the channels it has to appear on. Gives back: A version per channel, facts identical, phrasing appropriate.
  • Watcher: Monitors for a trigger, a threshold or an account going quiet, and surfaces it the day it happens. Takes in: A trigger, a threshold, or an account worth watching. Gives back: A notification the day it happens, with the context attached.
  • Call handler: Answers the calls nobody is free to take, captures what the caller actually wants, and either books the next step or hands the call to a person with the context already written down. Takes in: An inbound call, and the questions you would have asked. Gives back: A structured enquiry, and a booking or a warm handover.
  • Document reader: Turns an invoice, a contract, a statement or a scanned form into the fields the next step needs, with the original filed against the record. Takes in: A PDF, a photograph of a document, or an email attachment. Gives back: The fields you need, with the source document attached.
  • Deduplicator: Finds the same company or person recorded three times under three spellings, decides which record is the real one, and keeps the history from the others. Takes in: A list, a database, or two systems that disagree. Gives back: One record per real thing, with nothing thrown away.
  • Translator: Carries the same message into another language at the right register, which is a different job from translating the words. Built for markets where half the enquiries arrive in Arabic and half in English. Takes in: A message, a listing or a document, and the language it has to land in. Gives back: The same meaning, phrased the way that market expects.
  • Reviewer: Checks an output against your rules before it goes anywhere: the claims you are not allowed to make, the numbers that have to match the system of record, the tone you have settled on. Takes in: A draft, and the rules it has to satisfy. Gives back: A pass, or a specific objection a person can act on.
  • Scheduler: Finds a slot that works for everyone involved, sends the invitation, and handles the reschedule without a thread of six messages. Takes in: Two or more calendars and a purpose. Gives back: A booked slot, and a rebooked one when it moves.
  • Escalation router: Decides who a difficult case belongs to and says why, so the hard ones stop landing in the same inbox as the routine ones. Takes in: A case the routine path could not close. Gives back: An owner, a priority, and the reason for both.
  • Reconciler: Keeps two systems agreeing about the same fact, and raises the cases where they cannot both be right instead of silently picking one. Takes in: Two systems that hold overlapping records. Gives back: Agreement where it is safe, and a flagged exception where it is not.

Systems we build

01–23

Several functions running together, connected to the tools you already use and presented through software we build. Every system is scoped and built around the business it runs in. What follows is the shape of the work, not a specification.

  • In productionLarger build

    Revenue Orchestration

    For teams that sell outbound.

    Finds, qualifies and opens conversations. The discard rate is the point: a filtered list is not a pipeline.

    Assembled from
  • Built to orderStandard build

    Quote-to-Cash

    For businesses that quote bespoke work.

    Closes the gap between an enquiry arriving and a quote going out, makes pricing consistent regardless of who is quoting, and keeps a record of why the lost ones were lost.

    Assembled from
  • Built to orderStandard build

    Client Delivery & Reporting

    For agencies and services firms.

    Turns delivery into something the client can see, and the monthly report into something nobody has to assemble.

    Assembled from
  • Built to orderQuick build

    Inbound Triage

    For teams drowning in their own inbox.

    Reads what arrives, routes it to whoever owns it, answers what has been answered before from your own material, and escalates the rest with context.

    Assembled from
  • Built to orderStandard build

    Onboarding & Handover

    For firms where the first month decides the year.

    Runs the checklist, chases what is missing, and gives the client one place to see where things stand instead of a thread.

    Assembled from
  • Built to orderQuick build

    Renewal & Revival

    For businesses with a book of past clients.

    Watches the accounts that have gone quiet, surfaces the ones worth a conversation, and prepares the approach before anyone picks up the phone.

    Assembled from
  • Built to orderStandard build

    Market Intelligence

    For teams that need to know before the quarter ends.

    Tracks competitors, pricing and the signals that matter in your sector, and produces something readable rather than a feed.

    Assembled from
  • Built to orderLarger build

    Internal Operations Desk

    For back offices held together by memory.

    Moves work between systems that were never designed to talk, keeps both of them right, and escalates only the cases that do not fit.

    Assembled from
  • Built to orderQuick build

    WhatsApp Enquiry Desk

    For any business in a market where WhatsApp is the front door.

    Reads what arrives on WhatsApp, asks the two or three questions you would have asked, and either books the next step or hands a qualified enquiry to a person. Out of hours is the point: the enquiry is captured at the moment it is made rather than the next working morning.

    Assembled from
  • Built to orderQuick build

    Telegram Operations Desk

    For teams that already run on Telegram.

    The same job in the channel the team is actually in: enquiries triaged, approvals requested and recorded, and a searchable record of what was decided, without anybody moving to a tool they will not open.

    Assembled from
  • Built to orderStandard build

    Inbound Call Agent

    For businesses that lose calls they never hear about.

    Answers when nobody can, establishes what the caller wants, and books, answers or escalates. Every call arrives afterwards as a written record rather than as a missed-call notification, which is the part most businesses have never had.

    Assembled from
  • Built to orderStandard build

    Property Enquiry Desk

    For brokerages and developers.

    Matches an enquiry against what is actually available, answers the questions that do not need an agent, books the viewing, and passes the ones worth a person's time with the budget, the timeline and the shortlist already established.

    Assembled from
  • Built to orderQuick build

    Listing Syndication

    For anyone publishing the same thing to several portals.

    One listing, written once, adapted per portal, with the facts identical everywhere and the phrasing appropriate to each. Changes propagate, and so do withdrawals, which is the half people forget.

    Assembled from
  • Built to orderQuick build

    Listing & Client Revival

    For agencies with a back-book of past enquiries and listings that went quiet.

    Watches the enquiries and listings that have gone quiet, works out which are worth another look and why now, and prepares the approach before anyone picks up the phone.

    Assembled from
  • Built to orderStandard build

    Account Research Desk

    For B2B teams selling into a defined market.

    Builds the picture of an account before anyone speaks to it, watches for the change that makes now the moment, and prepares the approach. Most of what it finds is a reason not to bother, which is the expensive judgement to make by hand.

    Assembled from
  • Built to orderStandard build

    Tender & Proposal Desk

    For firms that answer the same questions in every submission.

    Assembles a first draft from what you have already answered elsewhere, flags the sections that genuinely need new writing, and keeps a record of which answers won and which did not.

    Assembled from
  • Built to orderStandard build

    Pipeline Revival

    For teams with a CRM full of records nobody is working.

    Finds the leads that went quiet, works out which are worth another conversation and why now, and prepares the approach. Most CRMs are mostly dormant records; the ones worth reopening are rarely the most recent.

    Assembled from
  • Built to orderQuick build

    Review & Reputation Desk

    For B2C businesses judged in public.

    Asks for the review at the moment it is most likely to be given, drafts a reply that sounds like the business rather than a template, and escalates anything that reads as a real complaint before it becomes a public one.

    Assembled from
  • Built to orderQuick build

    Repeat Purchase Desk

    For B2C businesses with a returning customer base.

    Notices when a customer is due, overdue or drifting, and reaches out at the point that is useful rather than on a fixed monthly calendar everyone has learned to ignore.

    Assembled from
  • Built to orderQuick build

    Competitor Watch

    For teams that keep finding out too late.

    Tracks a defined set of competitors for the things that would actually change a decision: pricing, positioning, hiring, launches, and what they have quietly stopped saying. Produces something readable on a schedule, not a feed.

    Assembled from
  • Built to orderStandard build

    Content & Search Desk

    For businesses that want to be found without buying every click.

    Works out what your market is actually searching for, briefs and drafts against it, publishes, and reports on what moved. Built around the pages that earn attention over years rather than the ones that need a budget to be seen at all.

    Assembled from
  • Built to orderQuick build

    Social & Channel Desk

    For businesses running several channels with one person.

    Adapts one piece of work per channel, schedules it, and brings the replies back into one place so the response happens on the day rather than the following week.

    Assembled from
  • Built to orderStandard build

    Recruitment Screener

    For teams hiring faster than they can read.

    Reads applications against the criteria that actually predict success in the role, shortlists with the reasoning attached, and books the first conversation. A person decides, and the reading is what gets removed.

    Assembled from
  • Revenue Orchestration is assembled from: Lead researcher, Qualifier, Follow-up manager.
  • Quote-to-Cash is assembled from: Enquiry reader, Quote preparer, Reviewer.
  • Client Delivery & Reporting is assembled from: Report builder, Scheduler, Reconciler.
  • Inbound Triage is assembled from: Enquiry reader, Qualifier, Escalation router.
  • Onboarding & Handover is assembled from: Document reader, Scheduler, Watcher.
  • Renewal & Revival is assembled from: Watcher, Lead researcher, Follow-up manager.
  • Market Intelligence is assembled from: Watcher, Report builder, Reviewer.
  • Internal Operations Desk is assembled from: Reconciler, Deduplicator, Escalation router.
  • WhatsApp Enquiry Desk is assembled from: Enquiry reader, Qualifier, Scheduler.
  • Telegram Operations Desk is assembled from: Enquiry reader, Escalation router, Reviewer.
  • Inbound Call Agent is assembled from: Call handler, Qualifier, Scheduler.
  • Property Enquiry Desk is assembled from: Enquiry reader, Qualifier, Scheduler.
  • Listing Syndication is assembled from: Listing writer, Translator, Reviewer.
  • Listing & Client Revival is assembled from: Watcher, Lead researcher, Follow-up manager.
  • Account Research Desk is assembled from: Lead researcher, Watcher, Qualifier.
  • Tender & Proposal Desk is assembled from: Document reader, Quote preparer, Reviewer.
  • Pipeline Revival is assembled from: Watcher, Lead researcher, Follow-up manager.
  • Review & Reputation Desk is assembled from: Watcher, Follow-up manager, Escalation router.
  • Repeat Purchase Desk is assembled from: Watcher, Qualifier, Follow-up manager.
  • Competitor Watch is assembled from: Watcher, Report builder, Translator.
  • Content & Search Desk is assembled from: Lead researcher, Listing writer, Report builder.
  • Social & Channel Desk is assembled from: Listing writer, Scheduler, Follow-up manager.
  • Recruitment Screener is assembled from: Document reader, Qualifier, Scheduler.
Case studies

The detail behind any of these, on request.

Each of these has a written breakdown: what the process looked like before, what we built, what a person still decides, and what it cost. They are not published because they contain a client's operating detail. Ask and we will send the one you want, with that client's agreement.

Request a case study

Start with
the diagnostic.

A scoping conversation costs nothing and ends with a straight answer about whether there's enough here to be worth doing. If there isn't, we'll tell you.

Questions. Asked before every engagement.

Your data is yours. You can export it at any time, and it is exported to you in a documented format before any engagement closes. The software itself is licensed: we build it around your business, host it, and run it, and you pay monthly for that. If you'd rather own it outright, that's possible. It's a different kind of engagement and it's priced accordingly. Licensing keeps maintenance our problem rather than yours, which is why it is the default.

Two weeks' notice, either side. Your data is yours. You can export it at any time, and it is exported to you in a documented format before any engagement closes. The system stops running. If you'd rather keep it running, the ownership option is available at that point as well. Ending the retainer doesn't force you to lose what was built.

Typically four to eight weeks from signing to a working system, depending on how many tools it connects to and what state the data is in. A scoping conversation and a written plan come first, so the timeline is agreed before anything is committed to.

Access to the tools and data the system will work with, one person who can make decisions, and a few hours in the first two weeks while we map how work actually moves through your business. After that, very little. The point of the engagement is that it runs without your attention.

Usually. Most business software exposes an interface we can build against, and where one doesn't there's normally a way around it. Which connections are viable is settled in the scoping conversation, so you find out before committing rather than after.

Hosting region for a system we build for you is decided at the start of the engagement, not inherited from a default. If data residency is a hard requirement, raise it in the first conversation and we will tell you plainly whether we can meet it. This website is separate and its processing is already fixed: enquiries, quote requests, bookings and chat are handled by Supabase in Tokyo, Resend in Tokyo, Cloudflare, cal.com and Moonshot AI, which the privacy policy names individually along with where each one processes. Nothing from a client system is ever sent to the chat assistant.

That's the normal starting point, and mapping them is part of the work. Automating a process nobody has examined just makes the confusion faster, so we don't start there. The first phase establishes how things actually happen, as opposed to how they're supposed to.