ProgrammableMarketing/sanka.com (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 7
  • This quarter · 12
  • Big bets · 2
  • Wildcards · 2
  • How we can help
Generated Nov 19, 2026
  1. Programmable
  2. Playbooks
  3. Sanka
Sanka logo

growth playbook · Nov 19, 2026

sanka.com (opens in a new tab)

Sanka growth playbook

Diagnosis

Sanka has turned from a back-office cloud ERP into an "IT problems" company in about a year, with Desk launched only weeks ago as the free front door, and it ships product updates almost twice a week. It already owns unusual assets: about 4,000 Signal research pages, 84 hand-written comparison guides in English and Japanese, a daily CIO newsletter, a free open-source scanner and a free IT job board.

The gaps are where these assets meet the buyer. The site currently states two different Desk prices, the Signal pages end in "More evidence needed" without pointing to the Migrate product that solves the move, Desk and Migrate have no customer proof while all six customer stories are about the older back-office product, and the contact form sends everyone to a migration call.

This playbook fixes the price first, turns Signal and the guides into routes to Desk and Migrate, and builds proof, then uses the Atlassian billing change, Monitor, MSPs and HubSpot partners to bring in buyers, with an end-of-life migration package and a public software price index as bigger bets.

Growth Score

6/10

Biggest Opportunity

Turn Sanka's own research traffic (Signal, guides, CIO Daily, Monitor reports) into Desk sign-ups and quoted Migrate projects, with one clear price and real proof on every page.

Biggest Risk

Five products and fast pivots with very little public proof: buyers comparing Sanka with Siit, Atomicwork, Freshservice or Jira Service Management see conflicting prices and no Desk results, and thin templated Signal pages could weaken trust in the strong guides.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Show one Desk price everywhere: the guides and changelog say "10 free AI resolutions a month, from US$1", the pricing page says 4,000 credits once and about $1.50 per action

    Decide the live Desk price model and write it in one paragraph, in English and Japanese.

    High impact First result in 2 weeks
  2. 2

    Run three Desk pilots and publish the first Desk result on the Desk page

    Ask the three most engaged current customers to pilot Desk.

    High impact First result in 6 weeks
  3. 3

    Turn the "More evidence needed" dead end on Signal alternatives pages into a Sanka Migrate estimate for the apps Migrate already moves

    Match the Migrate supported-platform list against the Signal alternatives slugs.

    High impact First result in 1 month

02

Your idea portfolio

23 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 7 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 1Big bets · 9Fill-ins · 6Reconsider · 7
Effort →

Showing 23 of 23 ideas

This week 7

Quick wins with a clear first action.

  • 01

    Sanka's comparison guides tell buyers to "read the bill before you move", and they list Desk at "10 free AI resolutions a month; Pro from US$1 per resolved ticket, no base fee". This week's product update says the same. But the Desk pricing page, the page those guides cite, still says 4,000 credits "once per workspace" and "600 credits / action" (about $1.50), so adding 10 people to a group costs about $15 there, against $1 for one resolved ticket in the guides. The words "10 free AI resolutions" and "per resolved ticket" do not appear on the pricing page. A buyer who checks both pages, as the guides invite them to, finds two different products.

    High impactLow effort First result in 2 weeks Founder & CEO

    First action

    Decide the live Desk price model and write it in one paragraph, in English and Japanese.

    How to measure it

    Pricing-and-guide-to-sign-up rate

    Now
    –
    Target
    +25%
    By
    60 days

    Steps

    1. 1

      Decide the model

      Per resolved ticket or per action; free monthly allowance or one-time credits; how credits map to tickets.

      Founder & CEO 1 day

    2. 2

      List every place

      Pricing pages, Desk page, homepage, guides, Japanese, Korean and Indonesian versions, console billing screen, docs.

      Product Marketing Lead half a day

    3. 3

      One source

      Move the numbers into one shared data file that all pages read.

      Web Engineer 2 days

    4. 4

      Rewrite pricing

      Plain price, a worked monthly example and a "Prices last changed" date.

      Product Marketing Lead 1 day

    5. 5

      Update guides

      Correct the Desk rows and answers in the ITSM guides and their Japanese versions.

      Content Editor 1 day

    6. 6

      Check the console

      Make sure the billing screen and receipts match the public price.

      Product Manager, Desk 1 day

    7. 7

      Measure

      Sign-up rate from pricing and guide pages before and after.

      Growth Lead weekly

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    Founder & CEO

    Smallest test

    Correct the Desk pricing page today to match the Week-47 update and watch sign-ups for two weeks.

    Why it works

    Decide which model is live (the Week-47 update suggests per resolved ticket), then make the Desk pricing page, the main pricing page, the Desk page, the homepage credit line, the four ITSM guides and their Japanese versions say exactly the same thing: what is free each month, what a resolved ticket costs, what joiner and leaver tickets cost, and how credits relate to tickets. Keep the price in one shared component or data file so the guides, the pricing pages and the console read the same numbers, add a "Prices last changed" date, and add a worked example (for example 200 requests a month, 120 resolved by Desk) to the pricing page.

    Price is the first thing a self-serve buyer checks, and Desk's main promise is "free". Two prices make a careful IT buyer doubt both, and the guides are the pages most likely to be read by people actively comparing tools. One clear, low, per-ticket price turns that research traffic into sign-ups.

    Ready to use

    ChecklistDesk price consistency check

    [ ] /pricing/desk/ shows the live model and a worked example
    [ ] /pricing/ Desk card matches
    [ ] /desk/ numbers section matches
    [ ] Homepage free-credit line matches
    [ ] Freshservice, ServiceNow, Jira Service Management and Zendesk guides: Desk rows and FAQ answers
    [ ] /ja/, /ko/ and Indonesian versions
    [ ] Console billing and receipts
    [ ] "Prices last changed" date on each pricing page

    Risks and how to handle them

    • Existing workspaces were sold on credits

      Honour their credits and explain the conversion in the console and by email.

    • The model changes again soon

      With one data file, the next change is a single edit.

    Evidence

    • Your websiteDesk pricing page (checked November 19, 2026): "4,000 Sanka Credits (≈ $10 / ¥1,000) to start, once per workspace, with no card and no contract"; Pro "600 credits / action", "≈ $1.50 / ¥150 for each action Sanka Bot runs on a system"; answers 50 credits; adding 10 people to a group is "6,000 credits" (≈ $15). The phrases "10 free AI resolutions" and "per resolved ticket" do not appear.Source
    • Your websiteProduct updates, 2026 Week-47: Desk pricing with 10 AI-resolved requests a month free and Pro "from US$1" (¥150) per ticket Desk resolves, US$3 for joiner and leaver tickets, no charge for tickets reopened within seven days. Earlier weeks: Desk launched in Week-45, Desk API and webhooks in Week-46-2, the CIO Daily newsletter in Week-44-2, Korean and Indonesian language support in Week-44, partner applications from the workspace in Week-47-2.Source
    • Your websiteComparison guides (Freshservice alternatives, ServiceNow alternatives, Jira Service Management pricing): Desk is listed at "10 free AI resolutions a month; Pro from US$1 per resolved ticket, no base fee"; the Freshservice guide runs to roughly 4,000 words with a 43-item source list, discloses "Sanka Desk is our own product", and dates itself "Sources read: November 9, 2026".Source
    • Your websiteHomepage: "Sanka — Free Desk. Smart AI."; five products (Desk, Flow, Monitor, Migrate, Cloud); "4,000 free Sanka Credits to start, with no card"; main CTA "Explore Sanka Desk". A November 2025 snapshot led with "AI-powered cloud ERP empowering backoffice".Source
  • 02

    Sanka publishes about 4,000 Signal pages, many of them "<app> alternatives" pages, which attract people who are thinking about leaving a tool. Every one checked (Zendesk, Jira, Close) ends with "More evidence needed" and eight template cards, and the article never mentions Sanka Migrate, even for Zendesk, Freshdesk, HubSpot, Salesforce or Jira Service Management, which Migrate lists as supported in either direction. The visitor most likely to need a migration gets no route to the product that does it.

    High impactMedium effort First result in 1 month Product Manager

    First action

    Match the Migrate supported-platform list against the Signal alternatives slugs.

    How to measure it

    Signal-to-Migrate starts

    Now
    –
    Target
    50 a month
    By
    90 days

    Steps

    1. 1

      Match apps

      Signal alternatives slugs that appear in Migrate's supported list.

      Data Engineer, Signal 1 day

    2. 2

      Write the block

      One sentence per app category plus the free dry run.

      Product Marketing Lead 1 day

    3. 3

      Add the estimator

      Records and mappings to credits and dollars or yen.

      Web Engineer 3 days

    4. 4

      Add Desk lines

      On help desk and ITSM app pages.

      Web Engineer 1 day

    5. 5

      Ship in both languages

      English and /ja/ pairs.

      Web Engineer 2 days

    6. 6

      Track

      Clicks and workspace starts by page.

      Growth Lead weekly

    First result
    1 month
    Cost
    About a week of engineering
    Owner
    Product Manager, Migrate

    Smallest test

    Add the block to the ten alternatives pages with the most traffic for apps Migrate supports.

    Why it works

    For every alternatives page whose app appears in Migrate's supported list, add a block under the verdict: "Moving off Zendesk? Sanka Migrate maps and moves your tickets, users and knowledge, with a dry run free." Include a two-field estimator (records, objects) using the published rate of 2 credits per record and 20 per AI mapping, and a link to the matching hand-written guide. For Desk-category apps (Zendesk, Freshservice, Jira Service Management, ServiceNow), add a second line for Desk.

    Alternatives searches are high intent, and Migrate's free dry run and per-record price are easy first steps. Sanka already pays to build these pages; the block makes them earn.

    Risks and how to handle them

    • Signal's neutral tone is lost

      Keep the verdict independent and label the block clearly as Sanka's own product.

    Evidence

    • Your websiteSignal alternatives pages (Zendesk, Jira, Close): each gives the verdict "More evidence needed" ("The available evidence is not enough to recommend a move") and eight template cards with the same "Shared category" label; the article body never mentions Sanka Desk or Sanka Migrate, and the Zendesk page does not link to Sanka's own Zendesk comparison guide; the Jira page lists project-management tools only.Source
    • Your websiteMigrate page: "moves CRM, ERP, accounting, ecommerce, and legacy systems to modern platforms" with "mapping, validation, and parallel-run diffing"; lists ServiceNow, Jira Service Management, Freshservice, Zendesk, Freshdesk, Salesforce, HubSpot, Pipedrive, NetSuite and more, in either direction; no prices, proof or customer stories; the only call to action is "Pricing".Source
    • Your websiteMigrate pricing: 20 credits per AI-generated mapping and 2 credits per successful record; manual mapping and dry runs are free; 4,000 starter credits that "never expire"; no worked example for a typical migration.Source
    • Your websiteSitemap index: ten child sitemaps including signal, signal-apps, signal-alternatives and signal-repos; the programmable.info crawl counted 4,219 URLs under /signal, with English and /ja/ pairs; the guides sitemap has 168 URLs (84 English, 84 Japanese), including Desk comparisons with Freshservice, Jira Service Management, ServiceNow and Zendesk.Source
  • 03

    Sanka has two libraries that do not talk to each other: 84 careful guides (the Freshservice one has about 4,000 words and 43 sources) and about 4,000 template Signal pages. The Zendesk alternatives page in Signal does not link to Sanka's own Zendesk comparison guide, and the Jira alternatives page lists only project-management tools, with no link to the Jira Service Management guides.

    Medium impactLow effort First result in 2 weeks Content Editor

    First action

    List the tools covered by the 84 guides and their matching Signal URLs.

    How to measure it

    Signal-to-guide clicks

    Now
    –
    Target
    3x
    By
    60 days

    Steps

    1. 1

      Map tools

      Guide to Signal app and alternatives URLs.

      Content Editor 1 day

    2. 2

      Design the box

      One line, one link, near the verdict.

      Web Engineer 1 day

    3. 3

      Add reverse links

      From guides to live Signal profiles.

      Content Editor 1 day

    4. 4

      Fix Jira

      A Jira Service Management line on the Jira page.

      Content Editor 1 hour

    5. 5

      Japanese pairs

      Same links on /ja/ pages.

      Web Engineer 1 day

    6. 6

      Measure

      Clicks and guide rankings.

      Growth Lead monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Content Editor

    Smallest test

    Link the Zendesk, Freshdesk, ServiceNow and Jira pages this week.

    Why it works

    Map each guide to the Signal app and alternatives pages for the same tools, and add a "Read our full comparison" box near the top of those Signal pages. Add the reverse link from each guide to the live Signal profile for current prices and incidents. On the Jira page, add a line for Jira Service Management buyers.

    Internal links pass visitors and search authority from thin pages to the strongest pages, and the guides already end with Desk and Migrate calls to action.

    Risks and how to handle them

    • Too many boxes on a page

      One guide link per page, the closest match only.

    Evidence

    • Your websiteSignal alternatives pages (Zendesk, Jira, Close): each gives the verdict "More evidence needed" ("The available evidence is not enough to recommend a move") and eight template cards with the same "Shared category" label; the article body never mentions Sanka Desk or Sanka Migrate, and the Zendesk page does not link to Sanka's own Zendesk comparison guide; the Jira page lists project-management tools only.Source
    • Your websiteSitemap index: ten child sitemaps including signal, signal-apps, signal-alternatives and signal-repos; the programmable.info crawl counted 4,219 URLs under /signal, with English and /ja/ pairs; the guides sitemap has 168 URLs (84 English, 84 Japanese), including Desk comparisons with Freshservice, Jira Service Management, ServiceNow and Zendesk.Source
    • Your websiteComparison guides (Freshservice alternatives, ServiceNow alternatives, Jira Service Management pricing): Desk is listed at "10 free AI resolutions a month; Pro from US$1 per resolved ticket, no base fee"; the Freshservice guide runs to roughly 4,000 words with a 43-item source list, discloses "Sanka Desk is our own product", and dates itself "Sources read: November 9, 2026".Source
  • 04

    Every one of Sanka's six published customer stories (inventory, purchasing, billing, accounting, reporting) is a back-office Flow story, and Flow has a clear price: Free, Pro at $99 (¥9,900) and Enterprise at $500 a month. Yet the Flow page has no customer names, no metrics, no price and no sign-up or demo button, only links to use-case pages. The proof sits on /customers, far from the product it proves.

    Medium impactLow effort First result in 2 weeks Product Manager

    First action

    Add the sign-up button and the price line to the Flow page.

    How to measure it

    Flow page conversion

    Now
    –
    Target
    +40%
    By
    60 days

    Steps

    1. 1

      Add buttons

      Start free and Talk to us.

      Web Engineer 2 hours

    2. 2

      Add prices

      Free, Pro and Enterprise in USD and JPY.

      Web Engineer 2 hours

    3. 3

      Pick quotes

      One line per customer story.

      Product Marketing Lead 1 day

    4. 4

      Tag stories

      Match each to Flow use-case pages.

      Product Marketing Lead 1 day

    5. 5

      Add numbers

      Ask each customer for one before-and-after figure.

      Customer Success Lead 3 weeks

    6. 6

      Measure

      Sign-ups from Flow pages.

      Growth Lead weekly

    First result
    2 weeks
    Cost
    $0
    Owner
    Product Manager, Flow

    Smallest test

    Add the button and the price line today.

    Why it works

    Add a short header to the Flow page with "Start free" and "Talk to us" buttons and the three plan prices, then a strip with the six customers and one quote each ("Now we can manage purchasing, billing, orders, and shipping in one place"). Tag each story with the Flow use-case pages it matches (inventory, purchasing, invoices) and show it there too.

    Visitors on a product page decide there; proof and a next step at that moment raise conversion, and the stories already exist.

    Risks and how to handle them

    • Flow distracts from Desk

      Keep Desk as the homepage lead; this only fixes the Flow page itself.

    Evidence

    • Your websiteFlow page: "What you can do with Sanka Flow" across sales, finance, procurement, HR, billing, inventory, quoting and approvals; no customer names, metrics, testimonials or pricing; no sign-up or demo button, only links to use-case pages.Source
    • Your websiteCustomer stories page: six stories (nomad's, Hakko Electronics, Colopl, Mokaru International, Pizza Hut Japan, TAIMATSU), about inventory, purchasing, billing, accounting and reporting; none about IT requests; no quantified results; reviews praise "Salesforce data migration" and HubSpot data integration; partner badges for Salesforce, HubSpot, Microsoft, Google Cloud, AWS, Snowflake and Shopify; versions in Japanese, Korean and Bahasa Indonesia.Source
    • Your websitePricing overview: Flow Free, Pro at $99 (¥9,900) and Enterprise at $500 (¥50,000) a month; Migrate and Cloud credit packs from $10 for 4,000 credits; Monitor free and open source; one credit balance is shared by Desk, Migrate and Cloud.Source
  • 05

    Desk is now the homepage lead, but the Desk page has no customer logos, case studies or testimonials, and none of the six customer stories is about IT requests. Rivals lead with numbers: Siit shows Monzo deflecting "28%" of tickets and Airalo automating 50%; Atomicwork shows Zuora with 50% fewer tickets.

    High impactMedium effort First result in 6 weeks Customer Success Lead

    First action

    Ask the three most engaged current customers to pilot Desk.

    How to measure it

    Desk page conversion

    Now
    –
    Target
    +30%
    By
    90 days

    Steps

    1. 1

      Pick pilots

      Three customers with an IT team and Slack or Google Workspace.

      Customer Success Lead 1 week

    2. 2

      Agree measures

      Resolved without IT, time to resolve, hours saved.

      Product Manager, Desk 2 days

    3. 3

      Run 30 days

      Weekly check-ins.

      Customer Success Lead 30 days

    4. 4

      Pull numbers

      From the Desk API.

      Product Manager, Desk 2 days

    5. 5

      Write the story

      Three numbers, one quote, in English and Japanese.

      Product Marketing Lead 1 week

    6. 6

      Publish

      Desk page, guides and MSP page.

      Web Engineer 1 day

    First result
    6 weeks
    Cost
    Credits for three pilots
    Owner
    Customer Success Lead

    Smallest test

    One pilot, one month, one published number.

    Why it works

    Pick three existing Flow or Migrate customers with an IT team, give them Desk with credits covered for 30 days, and measure requests answered, requests resolved without IT, median time to resolve and IT hours saved. Publish the best one as a short story with three numbers on the Desk page and in the guides, and the others as quotes. Use the Desk API and webhooks to pull the numbers automatically.

    A free product still needs proof that it works; one honest number from a real Japanese company beats any feature list, and it gives sales and partners something to show.

    Risks and how to handle them

    • Weak early numbers

      Publish what is true, and show the trend from week 1 to week 4.

    Evidence

    • Your websiteDesk page: "AI takes every request first. Your team keeps the decisions." Requests in Slack, Teams or email; changes in Google Workspace, Okta and Sanka Flow; "Teams has not yet run on a customer's tenant"; email requests can get answers but changes go to the IT team; answers in Japanese and English; no customer logos, case studies, testimonials or competitor comparisons on the page; CTA "Start now and ask your first question".Source
    • Your websiteCustomer stories page: six stories (nomad's, Hakko Electronics, Colopl, Mokaru International, Pizza Hut Japan, TAIMATSU), about inventory, purchasing, billing, accounting and reporting; none about IT requests; no quantified results; reviews praise "Salesforce data migration" and HubSpot data integration; partner badges for Salesforce, HubSpot, Microsoft, Google Cloud, AWS, Snowflake and Shopify; versions in Japanese, Korean and Bahasa Indonesia.Source
    • Competitor researchSiit, "The AI Service Desk": free trial and demo; customer results such as Monzo "28%" of tickets deflected and Airalo 50% automated; "Connects to 500+ tools"; ten customer stories.Source
    • Competitor researchAtomicwork, "AI Workforce for Enterprise IT": no public pricing, "Book a demo"; Zuora 50% fewer tickets and Pepper Money "replaced ServiceNow in 6 weeks"; 25+ languages.Source
  • 06

    The homepage leads with a free, self-serve Desk, but the contact page offers only a 30-minute call "about migration or implementation", requires a phone number, and has no way to say which of the five products the visitor wants, just a free-text box.

    Medium impactLow effort First result in 2 weeks Sales Lead

    First action

    Add the product picker field.

    How to measure it

    Form completion rate

    Now
    –
    Target
    +20%
    By
    45 days

    Steps

    1. 1

      Add the picker

      Six options, required.

      Web Engineer half a day

    2. 2

      Branch the form

      Migrate fields; Desk and Monitor instant links.

      Web Engineer 1 day

    3. 3

      Phone optional

      Ask for it only for Migrate and Cloud.

      Web Engineer 1 hour

    4. 4

      Route

      Each answer to its owner.

      Sales Lead half a day

    5. 5

      Translate

      Japanese, Korean and Indonesian versions.

      Product Marketing Lead 1 day

    6. 6

      Review

      Completion and call quality by product.

      Sales Lead monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Sales Lead

    Smallest test

    Add the picker and the Migrate fields this week.

    Why it works

    Add a required picker (Desk, Flow, Monitor, Migrate, Cloud, Partner) at the top of the form. Desk and Monitor answers get an instant link to start free and an optional call; Migrate answers get two extra fields (from which system, to which, rough record count) so the specialist arrives with an estimate; Partner answers go to the partner owner. Make phone optional.

    Routing by intent shortens the path for self-serve buyers and gives sales better calls; asking fewer required fields lifts completion.

    Risks and how to handle them

    • Fewer calls booked

      Track sign-ups from the instant links alongside calls.

    Evidence

    • Your websiteContact page: a 30-minute Zoom call "about migration or implementation"; no product picker, only a free-text "What would you like to cover?"; phone number required; available in English, Japanese, Korean and Bahasa Indonesia.Source
    • Your websiteHomepage: "Sanka — Free Desk. Smart AI."; five products (Desk, Flow, Monitor, Migrate, Cloud); "4,000 free Sanka Credits to start, with no card"; main CTA "Explore Sanka Desk". A November 2025 snapshot led with "AI-powered cloud ERP empowering backoffice".Source
  • 07

    The Freshservice guide already works out a 25-agent bill, but admits Sanka's per-ticket price "doesn't line up with these per-agent figures". Desk's real advantage, no base fee and no seat fees, is hard to see without the buyer's own numbers.

    Medium impactLow effort First result in 3 weeks Product Marketing Lead

    First action

    Write the formula from the agreed price model.

    How to measure it

    Calculator-to-sign-up rate

    Now
    –
    Target
    15%
    By
    60 days

    Steps

    1. 1

      Write the formula

      From the single price source.

      Product Marketing Lead 1 day

    2. 2

      Pull rival prices

      From the guides' sourced tables, with dates.

      Content Editor 1 day

    3. 3

      Build it

      Four inputs, two bills.

      Web Engineer 3 days

    4. 4

      Embed

      Desk pricing page and four ITSM guides.

      Web Engineer 1 day

    5. 5

      Pass to sign-up

      Carry the estimate into the new workspace.

      Product Manager, Desk 2 days

    6. 6

      Measure

      Use and sign-ups.

      Growth Lead weekly

    First result
    3 weeks
    Cost
    About a week of engineering
    Owner
    Product Marketing Lead

    Smallest test

    A static table of three company sizes on the pricing page.

    Why it works

    Once the price is settled (idea 1), add a calculator to the Desk pricing page and embed it in the ITSM guides: requests a month, share resolved by Desk, joiners and leavers a month, IT agents. It shows the Desk bill in USD or JPY and, beside it, the list-price per-agent bill from the guide's own sourced table. Let the visitor email the result to themselves or start a workspace with it.

    A buyer's own number is more convincing than a price table, and the comparison is already researched and sourced in the guides.

    Risks and how to handle them

    • Rival prices go out of date

      Show the date each price was read, as the guides already do.

    Builds on

    Evidence

    • Your websiteComparison guides (Freshservice alternatives, ServiceNow alternatives, Jira Service Management pricing): Desk is listed at "10 free AI resolutions a month; Pro from US$1 per resolved ticket, no base fee"; the Freshservice guide runs to roughly 4,000 words with a 43-item source list, discloses "Sanka Desk is our own product", and dates itself "Sources read: November 9, 2026".Source
    • Your websiteDesk pricing page (checked November 19, 2026): "4,000 Sanka Credits (≈ $10 / ¥1,000) to start, once per workspace, with no card and no contract"; Pro "600 credits / action", "≈ $1.50 / ¥150 for each action Sanka Bot runs on a system"; answers 50 credits; adding 10 people to a group is "6,000 credits" (≈ $15). The phrases "10 free AI resolutions" and "per resolved ticket" do not appear.Source

This quarter 12

The core plays for the next three months.

  • 08

    The HubSpot Signal page repeats the same description twice, shows "Confirm by quote" in every pricing field, marks entries "Review expired", and a HubSpot integration note says "Salesforce-specific Slack workflows are not confirmed as equivalent", text carried over from the Salesforce page. With about 4,000 such pages, search engines and readers may judge the whole site by them, including the strong guides.

    Medium impactMedium effort First result in 2 months Data Engineer

    First action

    Run a scan for other vendor names inside each vendor's notes.

    How to measure it

    Signal pages passing checks

    Now
    –
    Target
    100% of indexed pages
    By
    90 days

    Steps

    1. 1

      Write the checks

      Duplicates, wrong vendor names, expired markers, evidence count.

      Data Engineer, Signal 1 week

    2. 2

      Scan all pages

      English and Japanese.

      Data Engineer, Signal 2 days

    3. 3

      Noindex failures

      Until fixed.

      Web Engineer 1 day

    4. 4

      Fix top pages

      The 200 pages with the most traffic first.

      Data Engineer, Signal 3 weeks

    5. 5

      Refresh reviews

      A schedule for expired entries.

      Data Engineer, Signal ongoing

    6. 6

      Report

      Pass rate and impressions in Search Console.

      Growth Lead monthly

    First result
    2 months
    Cost
    Engineering time
    Owner
    Data Engineer, Signal

    Smallest test

    Fix the HubSpot and Salesforce pages and scan 100 pages for copied vendor names.

    Why it works

    Add automatic quality checks to the Signal generator: no duplicated paragraphs, no other vendor's name in a vendor's own notes, no expired review markers shown publicly (refresh or hide them), and at least a set amount of real evidence per page. Pages that fail are set to noindex until they pass. Track the share of indexed Signal pages that pass.

    Fewer, better pages build trust with readers and search engines, and Signal's own promise is to find system risks "before they reach your budget", which only works if readers trust the data.

    Risks and how to handle them

    • Traffic drops from noindexed pages

      Start with pages that get no clicks.

    Evidence

    • Your websiteSignal HubSpot page: the same description appears twice; every pricing field reads "Confirm by quote"; an integration note about HubSpot says "Salesforce-specific Slack workflows are not confirmed as equivalent"; several entries are marked "Review expired"; the migration verdict is "More evidence needed".Source
    • Your websiteSitemap index: ten child sitemaps including signal, signal-apps, signal-alternatives and signal-repos; the programmable.info crawl counted 4,219 URLs under /signal, with English and /ja/ pairs; the guides sitemap has 168 URLs (84 English, 84 Japanese), including Desk comparisons with Freshservice, Jira Service Management, ServiceNow and Zendesk.Source
    • Your websiteSignal hub: "Finding system risks before they reach your budget"; tracks price and contract changes, uptime, security notices, end-of-support dates and user feedback; "Our crawlers gather public data"; publishes Sanka Index results only as aggregates; points to Migrate, Flow and Cloud for acting on findings.Source
  • 09

    Atlassian says pay-as-you-go billing for Rovo credits takes effect on December 3, 2026, and Sanka's own CIO Daily already explained that Jira Standard's monthly allowance "covers 2.5 basic requests per user". Admins will soon see real usage and bills, which is the moment they compare alternatives.

    High impactMedium effort First result in 1 month Growth Lead

    First action

    Turn the CIO Daily issue into a standing checker page.

    How to measure it

    Jira-sourced Desk sign-ups

    Now
    –
    Target
    100
    By
    90 days

    Steps

    1. 1

      Check the facts

      Re-read Atlassian's published allowances and dates.

      Content Editor 1 day

    2. 2

      Build the checker

      Users, plan and requests in; allowance and Desk cost out.

      Web Engineer 1 week

    3. 3

      Switch page

      Desk plus Migrate, with a free dry run.

      Product Manager, Migrate 1 week

    4. 4

      Promote

      CIO Daily, guides, Signal Jira pages, LinkedIn.

      Growth Lead 2 weeks

    5. 5

      January follow-up

      "Your first bill" issue and emails.

      Content Editor 1 day

    6. 6

      Measure

      Checker use, sign-ups, Migrate dry runs.

      Growth Lead weekly

    First result
    1 month
    Cost
    About two weeks of staff time
    Owner
    Growth Lead

    Smallest test

    One CIO Daily follow-up issue with a simple checker table.

    Why it works

    Build a free "AI allowance checker" page: enter users, plan and monthly requests, see the expected allowance use and overage, and see what the same requests would cost on Desk. Pair it with a Jira Service Management to Desk switching page using Migrate (tickets, users, knowledge) and a free dry run. Promote it through CIO Daily, the Jira Service Management guides and the Signal Jira pages, and follow up in January when first invoices arrive.

    Price changes push buyers to look around, and Sanka already has the research, the help desk and the migration tool in one place.

    Risks and how to handle them

    • Atlassian changes allowances

      Date every number and link the source.

    Builds on

    Evidence

    • AtlassianAtlassian support: "On December 3, 2026, pay-as-you-go billing takes effect for Rovo credits"; admins can set spending limits, after which billable interactions pause.Source
    • Your websiteSanka CIO Daily (issues since October 23, 2026, signed by the founder): the November 18 issue, "Jira Standard's monthly Rovo allowance covers 2.5 basic requests per user", explains Atlassian's coming billing for Rovo credits and Automation, and ends with a P.S. for Sanka Desk.Source
    • Your websiteMigrate page: "moves CRM, ERP, accounting, ecommerce, and legacy systems to modern platforms" with "mapping, validation, and parallel-run diffing"; lists ServiceNow, Jira Service Management, Freshservice, Zendesk, Freshdesk, Salesforce, HubSpot, Pipedrive, NetSuite and more, in either direction; no prices, proof or customer stories; the only call to action is "Pricing".Source
  • 10

    Sanka launched CIO Daily a few weeks ago; issues are signed by the founder and turn hard pricing news into practical advice. The thousands of Signal pages and 84 guides are read by the same IT leaders, and they are the natural place to collect subscribers.

    Medium impactMedium effort First result in 1 month Content Editor

    First action

    Add the sign-up box to the guides.

    How to measure it

    Subscribers

    Now
    –
    Target
    +2,000
    By
    1 quarter

    Steps

    1. 1

      Design the box

      Page-specific promise.

      Web Engineer 2 days

    2. 2

      Roll out

      Guides first, then Signal.

      Web Engineer 1 week

    3. 3

      Japanese digest

      Weekly summary in Japanese.

      Content Editor weekly

    4. 4

      One product line

      Tied to the issue topic.

      Content Editor daily

    5. 5

      Repurpose

      Best issue on LinkedIn.

      Growth Lead weekly

    6. 6

      Track

      Subscribers to workspaces.

      Growth Lead monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Content Editor

    Smallest test

    Add the box to the four ITSM guides for two weeks.

    Why it works

    Add an inline CIO Daily sign-up box to every Signal page and guide, tailored to the page ("Get price and end-of-support changes for Zendesk and its rivals"). Keep one product line per issue, tied to the topic, and track subscribers who later start a workspace. Publish a weekly digest in Japanese and post the best issue on LinkedIn each week.

    A daily, useful newsletter builds trust with buyers long before they need Desk or Migrate, and research pages convert to email far better than to sign-up.

    Risks and how to handle them

    • Daily is too often for some

      Offer daily or weekly at sign-up.

    Evidence

    • Your websiteSanka CIO Daily (issues since October 23, 2026, signed by the founder): the November 18 issue, "Jira Standard's monthly Rovo allowance covers 2.5 basic requests per user", explains Atlassian's coming billing for Rovo credits and Automation, and ends with a P.S. for Sanka Desk.Source
    • Your websiteSitemap index: ten child sitemaps including signal, signal-apps, signal-alternatives and signal-repos; the programmable.info crawl counted 4,219 URLs under /signal, with English and /ja/ pairs; the guides sitemap has 168 URLs (84 English, 84 Japanese), including Desk comparisons with Freshservice, Jira Service Management, ServiceNow and Zendesk.Source
    • Your websiteProduct updates, 2026 Week-47: Desk pricing with 10 AI-resolved requests a month free and Pro "from US$1" (¥150) per ticket Desk resolves, US$3 for joiner and leaver tickets, no charge for tickets reopened within seven days. Earlier weeks: Desk launched in Week-45, Desk API and webhooks in Week-46-2, the CIO Daily newsletter in Week-44-2, Korean and Indonesian language support in Week-44, partner applications from the workspace in Week-47-2.Source
  • 11

    Monitor is a free, open-source scanner that runs with no account and sends nothing off the PC, and it already lists end-of-life business software and unsupported operating systems. Its only next step is to send the report to Sanka for a free review. The report knows exactly what needs to move, but does not say what moving would cost or how.

    High impactMedium effort First result in 2 months Product Manager

    First action

    Count how many sent reports last month listed end-of-life software.

    How to measure it

    Report-to-quote rate

    Now
    –
    Target
    10%
    By
    90 days

    Steps

    1. 1

      Size it

      End-of-life items in recent sent reports.

      Product Manager, Monitor 2 days

    2. 2

      Map targets

      Common end-of-life software to Migrate or Cloud paths.

      Product Manager, Migrate 1 week

    3. 3

      Add dates

      End-of-support dates from Signal.

      Data Engineer, Signal 1 week

    4. 4

      Local estimate

      Computed on the PC, nothing sent.

      Product Manager, Monitor 2 weeks

    5. 5

      Quote button

      User chooses what to send.

      Product Manager, Monitor 1 week

    6. 6

      Follow up

      Specialist replies within one business day.

      Sales Lead ongoing

    First result
    2 months
    Cost
    A few weeks of engineering
    Owner
    Product Manager, Monitor

    Smallest test

    Add end-of-support dates and a quote link to the one-page report only.

    Why it works

    For each end-of-life item in the report, add a line: the end-of-support date (from Signal), the modern target, and a rough Migrate or Cloud estimate in credits and yen, computed locally from the counts in the report. Add a single button to "Get a fixed quote for these items", which sends only the summary the user chooses. Show a Desk line for fleets with many joiner and leaver accounts.

    An offline scan earns trust; a concrete, local estimate turns that trust into a request at the moment the risk is in front of the IT lead.

    Risks and how to handle them

    • Feels like a sales tool

      Keep the estimate local and the send optional, as today.

    Evidence

    • Your websiteMonitor: a free Apache-2.0 app for Mac and Windows that reports unsupported operating systems, end-of-life business software and device security gaps as an Excel IT asset ledger or one-page risk report; "Nothing leaves the PC" unless the user sends a report; users can send the report to Sanka for a free review; optional console at monitor.sanka.com.Source
    • Your websiteSignal hub: "Finding system risks before they reach your budget"; tracks price and contract changes, uptime, security notices, end-of-support dates and user feedback; "Our crawlers gather public data"; publishes Sanka Index results only as aggregates; points to Migrate, Flow and Cloud for acting on findings.Source
    • Your websiteMigrate pricing: 20 credits per AI-generated mapping and 2 credits per successful record; manual mapping and dry runs are free; 4,000 starter credits that "never expire"; no worked example for a typical migration.Source
  • 12

    Sanka's MSP offer is generous (30% of what each client pays, for 36 months, with no resale and a white-label pilot), but the page itself says there is "no single view across clients yet": a technician must switch between client workspaces. For an MSP serving dozens of clients, that is the first objection.

    High impactHigh effort First result in 1 quarter Partnerships Lead

    First action

    Interview three MSPs about their must-have view across clients.

    How to measure it

    Active MSP partners

    Now
    –
    Target
    20
    By
    2 quarters

    Steps

    1. 1

      Interview MSPs

      What they need in one view.

      Partnerships Lead 1 week

    2. 2

      Build the console

      Tickets, approvals and credits by client.

      Product Manager, Desk 6 weeks

    3. 3

      Earnings example

      On the partner page.

      Product Marketing Lead 2 days

    4. 4

      Pilot kit

      One client, agreed requests, approvers, review.

      Partnerships Lead 1 week

    5. 5

      Recruit

      MSPs selling Google Workspace, Okta or Microsoft 365.

      Partnerships Lead ongoing

    6. 6

      Review

      Clients per partner and partner revenue.

      Founder & CEO monthly

    First result
    1 quarter
    Cost
    Six weeks of engineering plus partner time
    Owner
    Partnerships Lead

    Smallest test

    Sign three MSPs to a one-client pilot before building the console.

    Why it works

    Ship a partner console that lists every client workspace with open tickets, Desk-resolved share, pending approvals and credit balance, and lets a technician act without switching. Then run a recruiting push: a partner page with an earnings example, a one-client pilot kit (the page already suggests starting with one client), and outreach to MSPs already selling Google Workspace, Okta or Microsoft 365 in Japan.

    MSPs bring many small clients at once, and the revenue share is already attractive; removing the main workflow gap makes it easy to say yes.

    Risks and how to handle them

    • MSPs want a PSA connector first

      Ask in interviews and prioritize the most common PSA.

    Builds on

    Evidence

    • Your websiteMSP and MSSP page: partners earn "30%" of what each client pays Sanka for 36 months, no resale; white label is a pilot for Active partners; "no single view across clients yet"; claims 1,000+ companies supported and 13+ years; Desk answers in English and Japanese only.Source
    • Your websiteDesk page: "AI takes every request first. Your team keeps the decisions." Requests in Slack, Teams or email; changes in Google Workspace, Okta and Sanka Flow; "Teams has not yet run on a customer's tenant"; email requests can get answers but changes go to the IT team; answers in Japanese and English; no customer logos, case studies, testimonials or competitor comparisons on the page; CTA "Start now and ask your first question".Source
  • 13

    Customer reviews on the customers page praise Sanka's "Salesforce data migration" and HubSpot data integration. But the Migrate page has no prices, no proof and no customer stories, and its only call to action is "Pricing", where the per-record rate has no worked example.

    High impactMedium effort First result in 1 month Product Manager

    First action

    Ask the reviewing customer for permission to publish numbers.

    How to measure it

    Migrate dry runs

    Now
    –
    Target
    40 a month
    By
    90 days

    Steps

    1. 1

      Get permission

      From the Salesforce-to-HubSpot customer.

      Customer Success Lead 1 week

    2. 2

      Gather numbers

      Records, objects, days, issues caught.

      Product Manager, Migrate 2 days

    3. 3

      Write the story

      English and Japanese.

      Product Marketing Lead 1 week

    4. 4

      Worked example

      On the Migrate pricing page.

      Product Marketing Lead 1 day

    5. 5

      Estimator

      With dry-run and quote buttons.

      Web Engineer 1 week

    6. 6

      Next routes

      Two more stories.

      Product Manager, Migrate 1 quarter

    First result
    1 month
    Cost
    Staff time only
    Owner
    Product Manager, Migrate

    Smallest test

    Add one worked example to the Migrate pricing page this week.

    Why it works

    Turn the reviewed Salesforce-to-HubSpot project into a short Migrate story (records moved, objects, days, issues caught by parallel-run diffing). Add a worked example to the Migrate pricing page and an estimator on the Migrate page (objects, records, AI mappings), with a "Start a free dry run" button and a "Get a fixed quote" button. Repeat for the next two most common routes.

    Migration buyers fear risk and surprise cost; a real story and a transparent estimate address both, and the per-record price is already a strength.

    Risks and how to handle them

    • Estimates set wrong expectations

      Show a range and confirm after the free dry run.

    Evidence

    • Your websiteMigrate page: "moves CRM, ERP, accounting, ecommerce, and legacy systems to modern platforms" with "mapping, validation, and parallel-run diffing"; lists ServiceNow, Jira Service Management, Freshservice, Zendesk, Freshdesk, Salesforce, HubSpot, Pipedrive, NetSuite and more, in either direction; no prices, proof or customer stories; the only call to action is "Pricing".Source
    • Your websiteMigrate pricing: 20 credits per AI-generated mapping and 2 credits per successful record; manual mapping and dry runs are free; 4,000 starter credits that "never expire"; no worked example for a typical migration.Source
    • Your websiteCustomer stories page: six stories (nomad's, Hakko Electronics, Colopl, Mokaru International, Pizza Hut Japan, TAIMATSU), about inventory, purchasing, billing, accounting and reporting; none about IT requests; no quantified results; reviews praise "Salesforce data migration" and HubSpot data integration; partner badges for Salesforce, HubSpot, Microsoft, Google Cloud, AWS, Snowflake and Shopify; versions in Japanese, Korean and Bahasa Indonesia.Source
  • 14

    Sanka holds HubSpot Certified, Salesforce, Microsoft, Google Cloud, AWS, Snowflake and Shopify partner badges, and its reviews single out its Salesforce data migration. Other CRM agencies win the implementation but need the data moved; Migrate's per-record price makes it easy to resell as a line item.

    Medium impactMedium effort First result in 1 quarter Partnerships Lead

    First action

    Write a one-page partner offer with a sample co-branded report.

    How to measure it

    Partner-run migrations

    Now
    –
    Target
    15
    By
    2 quarters

    Steps

    1. 1

      Write the offer

      Discount, report, support.

      Partnerships Lead 1 week

    2. 2

      Sample report

      From a past migration, anonymized.

      Product Manager, Migrate 3 days

    3. 3

      List agencies

      HubSpot and Salesforce partners in Japan.

      Partnerships Lead 1 week

    4. 4

      Reach out

      Ten agencies, one pilot each.

      Partnerships Lead 1 month

    5. 5

      Run pilots

      With Sanka support.

      Product Manager, Migrate 1 month

    6. 6

      Review

      Volume and repeat use.

      Founder & CEO monthly

    First result
    1 quarter
    Cost
    Partner discount and staff time
    Owner
    Partnerships Lead

    Smallest test

    One agency, one co-branded migration.

    Why it works

    Create a partner offer for CRM and ERP agencies: they run Migrate under their project, pay the published per-record rate with a partner discount, and get a co-branded migration report from parallel-run diffing for their client. Recruit ten agencies from the HubSpot and Salesforce partner communities in Japan, starting with those that do not do migrations in-house.

    Agencies already have the deals; Sanka gets volume without a sales team, and each agency becomes a repeat channel.

    Risks and how to handle them

    • Channel conflict with Sanka's own services

      Agencies keep the client; Sanka supplies the engine.

    Builds on

    Evidence

    • Your websiteCustomer stories page: six stories (nomad's, Hakko Electronics, Colopl, Mokaru International, Pizza Hut Japan, TAIMATSU), about inventory, purchasing, billing, accounting and reporting; none about IT requests; no quantified results; reviews praise "Salesforce data migration" and HubSpot data integration; partner badges for Salesforce, HubSpot, Microsoft, Google Cloud, AWS, Snowflake and Shopify; versions in Japanese, Korean and Bahasa Indonesia.Source
    • Your websiteMigrate pricing: 20 credits per AI-generated mapping and 2 credits per successful record; manual mapping and dry runs are free; 4,000 starter credits that "never expire"; no worked example for a typical migration.Source
  • 15

    Sanka added Korean and Indonesian language support in Week-44, and the contact and customers pages exist in both. But the Desk and MSP pages say Desk answers in English and Japanese only. A Korean or Indonesian visitor can read the site, sign up, and then find that Desk cannot answer their employees in their language.

    Medium impactMedium effort First result in 1 month Founder & CEO

    First action

    Add a "Desk answers in English and Japanese" note to the Korean and Indonesian Desk pages.

    How to measure it

    KO/ID activated workspaces

    Now
    –
    Target
    25
    By
    1 quarter

    Steps

    1. 1

      Add the note

      Languages Desk answers in.

      Product Marketing Lead 1 hour

    2. 2

      Measure demand

      Traffic, sign-ups and activation by language.

      Growth Lead 30 days

    3. 3

      Pick one market

      Korea or Indonesia, or neither.

      Founder & CEO 1 day

    4. 4

      Add answers

      Knowledge answers in that language first.

      Product Manager, Desk 3 weeks

    5. 5

      Local proof

      One partner or customer.

      Partnerships Lead 1 month

    6. 6

      Paid test

      Local help desk search terms.

      Growth Lead 1 month

    First result
    1 month
    Cost
    Small paid test budget
    Owner
    Founder & CEO

    Smallest test

    Compare 30 days of Korean and Indonesian sign-ups with Japanese ones.

    Why it works

    Measure Korean and Indonesian traffic and sign-ups for 30 days. If demand is real in one market, add that language to Desk answers first (knowledge answers before system changes), publish one local partner or customer, and run a small paid search test on local help desk terms. Until then, say clearly on those pages which languages Desk answers in.

    Small, measured market tests avoid spreading a small team thin, while an honest language note prevents sign-ups that churn on day one.

    Risks and how to handle them

    • Spreading the team too thin

      Commit to one market only after the data.

    Evidence

    • Your websiteProduct updates, 2026 Week-47: Desk pricing with 10 AI-resolved requests a month free and Pro "from US$1" (¥150) per ticket Desk resolves, US$3 for joiner and leaver tickets, no charge for tickets reopened within seven days. Earlier weeks: Desk launched in Week-45, Desk API and webhooks in Week-46-2, the CIO Daily newsletter in Week-44-2, Korean and Indonesian language support in Week-44, partner applications from the workspace in Week-47-2.Source
    • Your websiteMSP and MSSP page: partners earn "30%" of what each client pays Sanka for 36 months, no resale; white label is a pilot for Active partners; "no single view across clients yet"; claims 1,000+ companies supported and 13+ years; Desk answers in English and Japanese only.Source
    • Your websiteContact page: a 30-minute Zoom call "about migration or implementation"; no product picker, only a free-text "What would you like to cover?"; phone number required; available in English, Japanese, Korean and Bahasa Indonesia.Source
  • 16

    Sanka is commendably honest: the Desk page says "Teams has not yet run on a customer's tenant", and the MSP page says the same for Microsoft Entra ID actions. Many companies run on Microsoft 365, and Sanka holds a Microsoft Solutions Partner badge, but today a Microsoft-only IT team reads that Desk is unproven for them.

    High impactMedium effort First result in 2 months Product Manager

    First action

    Ask current Flow customers on Microsoft 365 to be the first tenant.

    How to measure it

    Teams-connected workspaces

    Now
    –
    Target
    30
    By
    2 quarters

    Steps

    1. 1

      Find a partner

      A Microsoft 365 customer or MSP client.

      Customer Success Lead 2 weeks

    2. 2

      Scope actions

      Teams intake and five Entra ID actions.

      Product Manager, Desk 3 days

    3. 3

      Run 60 days

      With a named engineer.

      Product Manager, Desk 60 days

    4. 4

      Update pages

      Desk and MSP caveats.

      Product Marketing Lead 1 day

    5. 5

      Publish story

      Teams results.

      Product Marketing Lead 1 week

    6. 6

      Microsoft page

      A landing page for Microsoft 365 IT teams.

      Web Engineer 1 week

    First result
    2 months
    Cost
    Engineering time and covered credits
    Owner
    Product Manager, Desk

    Smallest test

    Teams intake for knowledge answers only, no system changes.

    Why it works

    Recruit one or two Microsoft 365 companies (or an MSP client) as design partners, with credits covered and a named engineer for 60 days. Run Teams intake and a small set of Entra ID actions (group membership, sign-outs, joiners and leavers) with approvals. When it works, update the Desk and MSP pages, publish a short Teams story, and add a Microsoft-focused landing page.

    One live tenant turns a caveat into proof and opens the Microsoft half of the market for both direct sales and MSPs.

    Risks and how to handle them

    • A failed action in a live tenant

      Start with approvals on every change and rollback enabled.

    Evidence

    • Your websiteDesk page: "AI takes every request first. Your team keeps the decisions." Requests in Slack, Teams or email; changes in Google Workspace, Okta and Sanka Flow; "Teams has not yet run on a customer's tenant"; email requests can get answers but changes go to the IT team; answers in Japanese and English; no customer logos, case studies, testimonials or competitor comparisons on the page; CTA "Start now and ask your first question".Source
    • Your websiteMSP and MSSP page: partners earn "30%" of what each client pays Sanka for 36 months, no resale; white label is a pilot for Active partners; "no single view across clients yet"; claims 1,000+ companies supported and 13+ years; Desk answers in English and Japanese only.Source
    • Your websiteCustomer stories page: six stories (nomad's, Hakko Electronics, Colopl, Mokaru International, Pizza Hut Japan, TAIMATSU), about inventory, purchasing, billing, accounting and reporting; none about IT requests; no quantified results; reviews praise "Salesforce data migration" and HubSpot data integration; partner badges for Salesforce, HubSpot, Microsoft, Google Cloud, AWS, Snowflake and Shopify; versions in Japanese, Korean and Bahasa Indonesia.Source
  • 17

    Real visitors pass Core Web Vitals (field LCP 2.49 s), so this is not urgent. But in Google's phone test the homepage scores 62, the largest element is a plain paragraph that takes 6.4 s, and the page loads 1.46 MB of JavaScript, with about 1.6 s of render-blocking requests and 431 KB of unused JavaScript. The same template serves thousands of Signal and guide pages, where many first-time visitors arrive on phones from search.

    Low impactMedium effort First result in 1 month Web Engineer

    First action

    Run PageSpeed on one Signal page and one guide page to confirm the same bundle.

    How to measure it

    Mobile lab LCP

    Now
    –
    Target
    under 3 s
    By
    60 days

    Steps

    1. 1

      Confirm the template

      PageSpeed on a Signal page and a guide.

      Web Engineer 1 hour

    2. 2

      Critical CSS

      Inline above-the-fold styles.

      Web Engineer 2 days

    3. 3

      Split the menu

      Load mega-menu code on interaction.

      Web Engineer 3 days

    4. 4

      Defer tags

      Tag manager after first paint.

      Growth Lead 1 day

    5. 5

      Cache assets

      Long cache lifetimes for static files.

      Web Engineer 1 day

    6. 6

      Re-test

      Lab and field numbers monthly.

      Web Engineer monthly

    First result
    1 month
    Cost
    About a week of engineering
    Owner
    Web Engineer

    Smallest test

    Defer the tag manager and re-run PageSpeed.

    Why it works

    Inline the critical CSS and defer the rest, split the navigation mega-menu (which lists every product, docs and solution) so its JavaScript loads on interaction, load the tag manager after first paint, and set long cache lifetimes for static assets. Measure on the homepage and on one Signal and one guide page.

    A faster first paint on search landing pages keeps more visitors reading, and one template fix improves thousands of pages.

    Risks and how to handle them

    • Deferred tags miss conversions

      Check conversion counts before and after.

    Evidence

    • PageSpeedGoogle PageSpeed, homepage (November 19, 2026): mobile score 62, desktop 75; lab LCP 6.4 s on phones, where the largest element is a paragraph of text; real visitors pass Core Web Vitals (field LCP 2.49 s, CLS 0); 2.6 MB and 97 requests, 1.46 MB of JavaScript; render-blocking requests cost about 1.6 s and unused JavaScript 431 KB; Google Tag Manager is 357 KB.Source
    • Your websiteSitemap index: ten child sitemaps including signal, signal-apps, signal-alternatives and signal-repos; the programmable.info crawl counted 4,219 URLs under /signal, with English and /ja/ pairs; the guides sitemap has 168 URLs (84 English, 84 Japanese), including Desk comparisons with Freshservice, Jira Service Management, ServiceNow and Zendesk.Source
  • 18

    Sanka runs Sanka Jobs, "the free job board for in-house IT roles", with listings from large Japanese and global employers. A company advertising for help desk or IT support staff has exactly the problem Desk solves, and the board is Sanka's own.

    Medium impactLow effort First result in 1 month Growth Lead

    First action

    Count help desk and IT support listings on the board this month.

    How to measure it

    Employer-sourced Desk sign-ups

    Now
    –
    Target
    20
    By
    1 quarter

    Steps

    1. 1

      Count roles

      Help desk and IT support listings.

      Growth Lead 1 day

    2. 2

      Write the note

      One line, no pressure.

      Product Marketing Lead 1 hour

    3. 3

      Posting flow

      Note in the flow and confirmation email.

      Web Engineer 2 days

    4. 4

      Job page box

      On help desk listings.

      Web Engineer 1 day

    5. 5

      Track

      Employer domains that sign up.

      Growth Lead monthly

    6. 6

      Follow up

      Offer a 15-minute setup call.

      Sales Lead ongoing

    First result
    1 month
    Cost
    $0
    Owner
    Growth Lead

    Smallest test

    Add the Desk box to help desk job pages for one month.

    Why it works

    When an employer posts or a listing is added for a help desk, IT support or joiner-and-leaver role, show the employer a short note in their posting flow and confirmation email: "While you hire, Desk can take routine requests in Slack or Teams for free." Add a Desk box on help desk job pages for IT managers browsing. Track employers who start a workspace.

    It reaches IT leaders at the moment they feel the workload, at no media cost, and turns a side project into a lead source.

    Risks and how to handle them

    • Employers dislike the upsell

      Keep it one line and only on IT support roles.

    Evidence

    • Your websiteSanka Jobs: "the free job board for in-house IT roles at companies around the world", operated by Sanka, listing IT roles at large Japanese and global employers.Source
    • Your websiteDesk page: "AI takes every request first. Your team keeps the decisions." Requests in Slack, Teams or email; changes in Google Workspace, Okta and Sanka Flow; "Teams has not yet run on a customer's tenant"; email requests can get answers but changes go to the IT team; answers in Japanese and English; no customer logos, case studies, testimonials or competitor comparisons on the page; CTA "Start now and ask your first question".Source
  • 19

    Desk is usage-priced with no seat fee, and one credit balance is shared with Migrate and Cloud. In usage pricing, the risk is that the admin only notices the bill. Desk already records every step and has an API, so it can show the value as clearly as the cost.

    Medium impactMedium effort First result in 2 months Product Manager

    First action

    Define the hours-saved estimate per request type.

    How to measure it

    Month-2 retention

    Now
    –
    Target
    +15%
    By
    2 quarters

    Steps

    1. 1

      Define measures

      Hours saved per request type.

      Product Manager, Desk 2 days

    2. 2

      Build the report

      From the audit log.

      Product Manager, Desk 1 week

    3. 3

      Email it

      Monthly, English and Japanese.

      Growth Lead 2 days

    4. 4

      Next suggestion

      One request type to automate.

      Product Manager, Desk 3 days

    5. 5

      Auto top-up

      Offer in the email.

      Product Manager, Desk 1 day

    6. 6

      Measure

      Retention by report opened.

      Growth Lead monthly

    First result
    2 months
    Cost
    About two weeks of engineering
    Owner
    Product Manager, Desk

    Smallest test

    Send a manual report to the first 20 workspaces.

    Why it works

    On the first of each month, email the admin (and show in the console): requests answered, requests resolved without IT, median time to resolve, estimated IT hours saved, credits used and balance, and the three request types that most often went to a human, with a suggestion to automate one. Offer auto top-up in the same email.

    A clear value report keeps usage-priced customers active, prompts them to automate more, and gives champions numbers to share internally.

    Risks and how to handle them

    • Hours saved looks inflated

      Show the assumption and let admins edit it.

    Builds on

    Evidence

    • Your websitePricing overview: Flow Free, Pro at $99 (¥9,900) and Enterprise at $500 (¥50,000) a month; Migrate and Cloud credit packs from $10 for 4,000 credits; Monitor free and open source; one credit balance is shared by Desk, Migrate and Cloud.Source
    • Your websiteProduct updates, 2026 Week-47: Desk pricing with 10 AI-resolved requests a month free and Pro "from US$1" (¥150) per ticket Desk resolves, US$3 for joiner and leaver tickets, no charge for tickets reopened within seven days. Earlier weeks: Desk launched in Week-45, Desk API and webhooks in Week-46-2, the CIO Daily newsletter in Week-44-2, Korean and Indonesian language support in Week-44, partner applications from the workspace in Week-47-2.Source

Big bets 2

Larger plays that can change the trajectory.

  • 20

    Sanka is the rare company that owns every step of an end-of-support project: a free scanner that lists end-of-life software, research that tracks end-of-support dates, and Migrate to move the systems. Today these are separate products with separate next steps.

    High impactHigh effort First result in 1 quarter Founder & CEO

    First action

    Pick the three most common end-of-life items in sent Monitor reports and price a fixed sweep for them.

    How to measure it

    EOL sweeps sold

    Now
    –
    Target
    10
    By
    2 quarters

    Steps

    1. 1

      Pick the items

      Most common end-of-life software from Monitor.

      Product Manager, Monitor 1 week

    2. 2

      Design tiers

      By number of systems.

      Founder & CEO 1 week

    3. 3

      Write the playbook

      Scan, report, plan, move, support.

      Product Manager, Migrate 2 weeks

    4. 4

      Landing page

      With a sample report.

      Product Marketing Lead 1 week

    5. 5

      Partner channel

      Offer to MSPs and CRM partners.

      Partnerships Lead 1 month

    6. 6

      First three

      Deliver, measure and publish.

      Customer Success Lead 1 quarter

    First result
    1 quarter
    Cost
    Delivery capacity and partner margin
    Owner
    Founder & CEO

    Smallest test

    Offer one fixed sweep to five companies that sent Monitor reports.

    Why it works

    Package a fixed-price "end-of-life sweep" for mid-sized Japanese companies: a fleet scan with Monitor, a dated risk report from Signal, a migration plan with free dry runs, and fixed-price moves with parallel-run checks, then Desk for the follow-up requests. Price in tiers by number of systems, sell through MSPs and partners, and publish an anonymized before-and-after.

    End-of-support dates create a deadline and a budget line, and one vendor with one quote is easier to approve than four.

    Risks and how to handle them

    • Fixed prices on messy legacy systems

      Price only after the free dry run, with clear scope limits.

    Builds on

    Evidence

    • Your websiteMonitor: a free Apache-2.0 app for Mac and Windows that reports unsupported operating systems, end-of-life business software and device security gaps as an Excel IT asset ledger or one-page risk report; "Nothing leaves the PC" unless the user sends a report; users can send the report to Sanka for a free review; optional console at monitor.sanka.com.Source
    • Your websiteSignal hub: "Finding system risks before they reach your budget"; tracks price and contract changes, uptime, security notices, end-of-support dates and user feedback; "Our crawlers gather public data"; publishes Sanka Index results only as aggregates; points to Migrate, Flow and Cloud for acting on findings.Source
    • Your websiteMigrate page: "moves CRM, ERP, accounting, ecommerce, and legacy systems to modern platforms" with "mapping, validation, and parallel-run diffing"; lists ServiceNow, Jira Service Management, Freshservice, Zendesk, Freshdesk, Salesforce, HubSpot, Pipedrive, NetSuite and more, in either direction; no prices, proof or customer stories; the only call to action is "Pricing".Source
  • 21

    Signal already tracks price and contract changes, uptime, security notices and end-of-support dates across thousands of apps, and Sanka publishes Index results only as aggregates. CIO Daily shows there is an audience for clear analysis of vendor price moves. Nobody publishes a regular, sourced index of SaaS price changes for Japan.

    High impactHigh effort First result in 1 quarter Data Engineer

    First action

    Draft the five headline charts from existing Signal data.

    How to measure it

    Report downloads

    Now
    –
    Target
    1,500 per edition
    By
    2 quarters

    Steps

    1. 1

      Pick measures

      Price changes, AI meters, end-of-support dates.

      Data Engineer, Signal 1 week

    2. 2

      Check quality

      Only verified, dated sources.

      Data Engineer, Signal 2 weeks

    3. 3

      Write it

      Japanese and English.

      Content Editor 2 weeks

    4. 4

      Launch

      Press release, CIO Daily, webinar.

      Growth Lead 1 week

    5. 5

      Follow up

      Offer a stack check to readers.

      Sales Lead ongoing

    6. 6

      Repeat

      Every quarter.

      Data Engineer, Signal quarterly

    First result
    1 quarter
    Cost
    Staff time and PR support
    Owner
    Data Engineer, Signal

    Smallest test

    One CIO Daily issue with three index charts.

    Why it works

    Publish a quarterly report: the share of tracked apps that raised prices, the median increase by category, new AI meters and usage charges, end-of-support dates in the next 12 months, and yen-versus-dollar effects. Release it in Japanese and English with a press release, a CIO Daily special and a webinar, gated only for the full data file.

    Original data earns press coverage, links and trust, and every reader who finds a price rise in their stack is a candidate for Migrate or Desk.

    Risks and how to handle them

    • Errors damage credibility

      Publish sources and methods; correct openly.

    Builds on

    Evidence

    • Your websiteSignal hub: "Finding system risks before they reach your budget"; tracks price and contract changes, uptime, security notices, end-of-support dates and user feedback; "Our crawlers gather public data"; publishes Sanka Index results only as aggregates; points to Migrate, Flow and Cloud for acting on findings.Source
    • Your websiteSanka CIO Daily (issues since October 23, 2026, signed by the founder): the November 18 issue, "Jira Standard's monthly Rovo allowance covers 2.5 basic requests per user", explains Atlassian's coming billing for Rovo credits and Automation, and ends with a P.S. for Sanka Desk.Source

Wildcards 2

Unexpected experiments, each with a cheap way to test it.

  • 22

    Sanka open-sourced a CLI runtime for code migrations ("Open source runtime to migrate DRF to FastAPI"), with scan, plan, apply, test and verify running locally without a token and a python-to-golang extension. It had 3 stars and 1 fork when checked: the developer audience has not been told yet.

    Medium impactMedium effort First result in 1 month Product Manager

    First action

    Write the launch post and the benchmark page.

    How to measure it

    CLI-sourced Cloud enquiries

    Now
    –
    Target
    15
    By
    1 quarter

    Steps

    1. 1

      Benchmark page

      Method, results, limits.

      Product Manager, Cloud 1 week

    2. 2

      Demo video

      Five minutes, a sample app.

      Product Manager, Cloud 3 days

    3. 3

      Launch post

      English and Japanese.

      Content Editor 3 days

    4. 4

      Share

      Python and FastAPI communities.

      Growth Lead 1 week

    5. 5

      Cloud link

      In CLI output and README.

      Product Manager, Cloud 1 day

    6. 6

      Measure

      Stars, installs, Cloud enquiries.

      Growth Lead monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Product Manager, Cloud

    Smallest test

    One launch post and one community share.

    Why it works

    Write a clear launch post and a public benchmark page (synthetic migrations, pass rates, how verify compares old and new responses), record a five-minute demo migrating a sample app, and post it in Python and FastAPI communities and developer newsletters. Add a "Need it run and hosted?" link to Sanka Cloud in the CLI's final output and the README.

    Developers who try the free CLI on a real codebase become the internal champions for paid Cloud projects.

    Risks and how to handle them

    • Too niche an audience

      Measure, and widen to the next extension if interest is thin.

    Evidence

    • Open sourceGitHub sankaHQ/sanka: "Open source runtime to migrate DRF to FastAPI (and more to come)"; scan, plan, apply, test and verify run locally without a token; extensions include python-to-golang; 3 stars and 1 fork when checked.Source
    • Your websitePricing overview: Flow Free, Pro at $99 (¥9,900) and Enterprise at $500 (¥50,000) a month; Migrate and Cloud credit packs from $10 for 4,000 credits; Monitor free and open source; one credit balance is shared by Desk, Migrate and Cloud.Source
  • 23

    All of Sanka's usage products draw on one shared credit balance, and credits for Migrate and Cloud never expire. That makes credits an ideal referral reward: cheap for Sanka to give, useful to any customer, and it pulls the referrer into another product.

    Medium impactLow effort First result in 2 months Growth Lead

    First action

    Decide the reward size and the activation event.

    How to measure it

    Referred workspaces

    Now
    –
    Target
    10% of new workspaces
    By
    2 quarters

    Steps

    1. 1

      Set rules

      Reward, activation event, caps.

      Founder & CEO 1 day

    2. 2

      Build links

      Per workspace, with tracking.

      Web Engineer 1 week

    3. 3

      Grant credits

      Automatically on activation.

      Web Engineer 3 days

    4. 4

      Place the link

      Monthly report, post-migration email, console.

      Growth Lead 2 days

    5. 5

      Exclude partners

      No double rewards.

      Partnerships Lead 1 day

    6. 6

      Measure

      Referred share of new workspaces.

      Growth Lead monthly

    First result
    2 months
    Cost
    Credits given away
    Owner
    Growth Lead

    Smallest test

    Email the link to current customers after their next successful migration.

    Why it works

    Give each workspace a referral link: when a referred company activates Desk or completes a Migrate dry run, both workspaces get credits (for example 4,000 each). Show the link in the monthly Desk report, after a successful migration, and in the partner console. Cap rewards per workspace and exclude partners already on revenue share.

    IT leaders talk to peers, and a reward that funds their own next project is more motivating than a gift card.

    Risks and how to handle them

    • Abuse with fake workspaces

      Reward only on real activation, with caps.

    Builds on

    Evidence

    • Your websitePricing overview: Flow Free, Pro at $99 (¥9,900) and Enterprise at $500 (¥50,000) a month; Migrate and Cloud credit packs from $10 for 4,000 credits; Monitor free and open source; one credit balance is shared by Desk, Migrate and Cloud.Source
    • Your websiteMigrate pricing: 20 credits per AI-generated mapping and 2 credits per successful record; manual mapping and dry runs are free; 4,000 starter credits that "never expire"; no worked example for a typical migration.Source

03

How Programmable can help

Where an idea in this playbook is something Programmable builds or runs, it's listed here with what we'd do. Everything else is yours to run.

ProgrammableDigital

Show it, don't just describe it

These ideas need something to show: a demo, a video, an animation, graphics or a deck. Digital turns screenshots or the site into all of them, in the company's own brand.

Make a demo (opens programmable.digital in a new tab)
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • LiveScore Group growth strategyParent of the LiveScore football scores and media app and website (live scores, news, video highlights, audio commentary, free-to-play…21 growth ideas
  • OpenEye growth strategyCloud video surveillance: the OpenEye Web Services (OWS) platform, cameras, recorders and AI analytics (AI Visual Search, AI Visual Check…21 growth ideas
  • Vervaunt growth strategyA London and New York eCommerce consultancy and performance marketing agency for luxury and premium brands: replatforming and platform…23 growth ideas
  • Yoodli growth strategyAn AI roleplay and coaching platform ("the AI Platform for Human Skills") where people practise sales calls, demos, interviews…21 growth ideas
  • GuppShupp growth strategyAn AI chat companion app for India in Hinglish, with five specialist companions for astrology, women's health, men's health, English…20 growth ideas
  • Nexshift.ai growth strategyAn AI customer engagement platform: AI voice agents, WhatsApp and web chat bots, SMS and a built-in CRM that follow up leads, collect…22 growth ideas
  • Zalos growth strategyComputer agents for finance operations: AI workers that log into ERPs, banks, portals and desktop finance tools the way a person does, run…22 growth ideas
  • Sol de Janeiro growth strategyA Brazilian-inspired body care and fragrance brand: Brazilian Bum Bum Cream, Cheirosa perfume mists, jelly balms, hair care, candles and…21 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 19, 2026, and cites them throughout. Sanka did not commission, review or endorse it, and Programmable is not affiliated with Sanka. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Sanka runs its business.

Something wrong, or do you represent Sanka? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 307 ideas

    One Desk price everywhere, a cost calculator, contact routing, Signal links to Migrate and the guides, a Flow sign-up path and the first Desk proof.

  2. Days 31 to 6012 ideas

    Clean the Signal templates, ride the Atlassian billing change, grow CIO Daily, connect Monitor to Migrate, scale MSP and HubSpot partners, give Migrate proof, check Korean and Indonesian demand, prove Teams, speed and the jobs board, and the monthly Desk report.

  3. Days 61 to 904 ideas

    Commit to the big bets: an end-of-life migration package and a public software price index; test the open-source developer launch and credit referrals.

The research behind the plan

2 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value quick, flexible support tailored to their needs. The most cited problem: paper and Excel-based management reaching its limit.

  • Careful Salesforce-to-HubSpot data migration
  • Manual reporting
  • In their words: “back office”

Market

Competitive landscape

5 competitors compared: Siit, Atomicwork, Freshservice, Jira Service Management and 1 more.

  • Gap to exploit: A free AI help desk with no seat fees for Japanese small and mid-sized companies
  • Siit: No public prices on the homepage
  • Atomicwork: Demo-only, enterprise-focused buying

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks firstNew accounts get 100,000 free enrichment credits with code BETA100K (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammableMediaAn AI note taker, interpreter and webinar host for your calls (opens programmable.media in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence