Garchi CMS company information and prospect research

A search for Garchi CMS prospect company information can mean two different tasks: researching the business behind the CMS, or finding businesses that use the CMS and might buy your service. Resolve that distinction before building a list. A software vendor, its own demonstration website and an independent deployment are different kinds of accounts.

For the first task, the official company identity and public contact below provide a useful starting point. For the second, there are public implementation stories you can investigate, but a historic case study is only the beginning of qualification. This guide does not present an exhaustive customer database or a live list of companies shopping for a new CMS.

The official About page identifies LumenHarbor Digital Solutions Limited as Garchi's developer and Aditya Kadam as its founder. Match that product identity to a stable company identifier before combining records from directories.

Information	Public evidence	How to use it
Product	Garchi CMS, a hosted headless CMS	Separate the software brand from a company legal name
Website operator	LumenHarbor Digital Solutions Limited	Identify the organization operating the product website
UK company number	13470710	Use as a deduplication key for this legal entity
Registry status and incorporation	Active; incorporated 22 June 2021, as shown in Companies House when checked for this guide	Recheck before making a current business decision
Previous legal name	ADIRANI DIGITAL SOLUTIONS LTD, 22 June 2021–11 July 2025, in the registry name history	Retain the old name as an alias rather than creating another account
Registered office	The Old Court House, Clark Street, Morecambe, Lancashire, LA4 5HR, United Kingdom, in the company record	Label it as a registered office; do not assume an operating headquarters
Public contact	Official contact form and support@garchi.co.uk	A published company support route, not a founder's direct inbox

These facts were reviewed on 3 October 2026. The registry itself notes that Companies House does not check the accuracy of filed information. A registration record helps resolve identity; it does not validate a sales opportunity, team size, revenue or email delivery.

Garchi's documentation overview describes structured pages, reusable sections and data items delivered through APIs. Its homepage also describes a dashboard for editors, REST access for applications and MCP access for compatible agents. These are content management capabilities. They should not be interpreted as a business contact database.

If your offer concerns content operations, migration, frontend development or editorial workflows, CMS usage may be a relevant context. If you sell unrelated local services, the CMS name alone is a weak qualification criterion. Decide what actual business problem your offer addresses before you collect technology labels.

The following are dated public examples, with their scope kept explicit. They are not independently tested current installs.

Company or project	Source and date	What the source establishes	What still needs checking
LumenHarbor website	Official Wix migration case study, 4 July 2024	The vendor reports moving its own website content to its in-house Garchi product	Present deployment and site ownership; this is a vendor example, not an independent customer
Sweqlink website	Official WordPress migration case study, 3 July 2024	The vendor reports transferring website content to Garchi while rebuilding the frontend	Current usage, the relevant legal entity and a present content or technical contact

The LumenHarbor article is particularly useful for account classification: it explicitly describes Garchi as an in-house product. Counting that deployment as an unrelated buyer would inflate your prospect list. The Sweqlink story gives a separate implementation to investigate, but its 2024 publication date does not establish that the same stack is running today.

Neither case study provides a current purchasing signal. Do not turn a migration story into a claim that the company now wants another migration, is dissatisfied with its CMS or has an allocated project budget.

The Apps Run The World Garchi page displays three entries: adirani Digital Solutions, LumenHarbor United Kingdom and Sweqlink United Kingdom. Its visible table gives company fields and deployment narratives; its buyer-intent table showed no rows in our review. Those are directory observations, not independent confirmation of each underlying claim.

That page supplies candidate names, but qualification requires another step. Companies House links the former adirani legal name to the current LumenHarbor name. Investigate whether the directory rows represent the same legal entity before treating them as distinct accounts. Do not merge solely because names sound similar; confirm the identifier or an official brand relationship.

For any paid customer list, request a small sample and ask:

• What is the source URL and last verification date for each deployment?
• Does the row describe a customer, vendor, implementation partner or demonstration site?
• Which field resolves the company to its domain and legal entity?
• Are employee and revenue figures observed, estimated or inferred?
• Does a named person have a current published role, and where was the contact obtained?

Review those answers against your target market before judging the usable record count. A detailed-looking table can still contain stale entries or duplicate accounts.

Start with explicit evidence: a current company statement, an implementation article identifying the exact domain, or a publicly available repository clearly connected to that company. A page that merely mentions Garchi as one option is a research lead, not proof of adoption.

For a technical cross-check, Garchi's Next App Router documentation demonstrates a server component fetching content from Garchi and an editor script loaded from its domain. This illustrates why client-side inspection can be incomplete: a server-rendered site may receive CMS content without exposing that fetch to a visitor's browser.

An observed Garchi resource on the exact website can support investigation, but check what loads it and whether it belongs to the live implementation. A demo, embedded example or leftover integration code can create a misleading signal. Conversely, finding no public script does not establish that the company is not using Garchi. Never try to obtain private API keys or access its CMS account to settle a prospecting question.

Keep a simple evidence status rather than a single confident-looking technology flag:

Status	Meaning	Next action
Current explicit evidence	A recently checked company-owned source states usage for the relevant site	Save the source and date; verify commercial fit separately
Historical deployment	A dated implementation story documents past usage	Recheck current usage before describing the stack in outreach
Technical clue	A public resource or repository suggests a connection	Corroborate the domain, context and deployment date
Unconfirmed mention	Garchi appears without a clear adoption claim	Keep in research, outside the confirmed-user segment
Unknown	No usable evidence found	Leave the technology conclusion open

1. Define the segment and the offer

Specify geography, company type, service fit and any required current-use evidence. Decide whether vendors and agencies belong in the segment. For a CMS migration offer, a documented past migration is background; a current project announcement or direct conversation would be a stronger next step.

2. Resolve the account before finding people

Match the official domain, current brand and legal entity. Keep historical names in aliases. Two domains can belong to one company; one company can have multiple websites. Deduplicate accounts by confirmed identity while retaining site-level deployment records.

3. Capture the adoption evidence

Save the exact page, the wording supporting usage, its publication date and your review date. Attach the evidence to the specific website or application. A claim about a marketing website should not become a claim about every product owned by the company.

4. Identify the role relevant to your offer

Use published team, leadership or contact pages. A founder may be appropriate for a small company, while a content lead or technical lead may own a CMS project elsewhere. Preserve the stated title. Do not relabel every founder or executive as the current legal owner.

5. Research the public contact separately

Record whether an address is a person's published business email, a departmental mailbox or a general support route. Keep its source and review time. A support address can help route a product question, but it does not establish permission, interest or access to the budget holder. A discovered address also does not prove mailbox deliverability.

6. Gate the shortlist before export

Use separate decisions for identity, technology, service fit and contact readiness. Move uncertain identities to review; remove duplicate accounts; leave unavailable fields blank. A company can be a good service fit while its CMS remains unknown, or a confirmed user while being a poor commercial fit.

7. Recheck the claims you will actually mention

Before outreach, reopen the current contact source and any technology evidence used in the message. If usage remains historical, describe it that way. Ask a relevant question without claiming an unobserved problem.

For example, after reviewing the dated Sweqlink case study: “I read the 2024 article about your move from WordPress to Garchi. Are you still using that content setup, and who handles content workflow improvements today?” This is an example question, not a message sent to the company or proof that it needs your service.

Use one record per account with a separate website field. These are suggested research fields, not a promise that every column is generated by a product.

Field	Fill in
Current company name and aliases	______
Official domain and relevant site	______
Legal identifier and source	______
Account relationship: independent / vendor / partner / unknown	______
Garchi evidence status	______
Adoption source URL and supporting wording	______
Source publication date and date reviewed	______
Current business problem observed	______
Offer fit and reason	______
Person and exact published role	______
Person source URL and date reviewed	______
Public contact, type, source URL and date	______
Delivery check status, if performed separately	______
Duplicate key and exclusion reason	______
Next action: research / review / contact / exclude	______

A worked classification from the sources above would group the confirmed old and current legal names under company 13470710, label the vendor's website as a vendor deployment, and leave current install status open. Sweqlink would remain a separate historical deployment candidate pending identity, current-use and contact checks. This prevents three directory rows from automatically becoming three qualified prospects.

Once you have independently researched the domains, OwnerClue domain enrichment can inspect public websites for contacts and supported people records. The field guide explains source URLs, capture dates and row review states. Keep your CMS research in the worksheet alongside that contact evidence.

OwnerClue does not offer a verified Garchi customer database or a dedicated Garchi detection filter. It does not infer revenue, prove current CMS contracts or replace mailbox delivery checks. Use the data-source guide to understand what an observed contact supports before you export it.

Who owns or operates Garchi CMS?

The official site identifies LumenHarbor Digital Solutions Limited as its operator and developer. Companies House records that legal entity under number 13470710. A product operator and a person's legal shareholding are separate questions; this guide does not claim to establish beneficial ownership.

Is adirani a different prospect from LumenHarbor?

The company registry records ADIRANI DIGITAL SOLUTIONS LTD as LumenHarbor's previous legal name. Match a directory record to that company number and official domain before merging it. Keep the prior name for search and historical-source matching.

Can I get a complete, current list of Garchi users here?

No complete current-user count is established by the public sources reviewed. The dated case studies are starting points. Ask any list provider for record-level evidence, dates and duplicate handling before relying on its coverage claims.

Does CMS usage mean a company is a sales prospect?

It establishes possible technical relevance when supported by evidence. Qualification still needs a suitable business, a relevant offer, a present contact route and a reason to start a conversation. Keep buying intent unknown until you have separate evidence.