Alienstacks Co., Ltd. — Bang Na, Bangkok · Tokyo
EN / 日本語Contact
CONTACT · お問い合わせ

Write to the engineers, not a sales team.

One inbox, read by the people who would design and build your system. Initial consultations are 30 minutes and carry no obligation, in English or 日本語, and we reply within one business day.

Reply within one business dayEnglish · 日本語Bang Na, Bangkok · TokyoNo obligation
Email us

Email is the only channel we use, so nothing gets lost between a form and an inbox. Write in as much or as little detail as you like — there is a checklist further down if you want one.

contact@alienstacks.com
SEND A MESSAGE

Tell us what you are trying to build.

This goes straight to the engineering inbox — no CRM, no sales sequence. If you would rather use your own email client, write to us directly.

The only way we can reply to you.
Describe it as a workflow rather than a feature list. No specification or budget figure needed.
Or email contact@alienstacks.com
BEFORE YOU WRITE

Make the first email do the work of a meeting.

You do not need a specification, a budget figure, or a deck. A few honest paragraphs about the problem are enough — but the more of the list below you include, the more useful our first reply will be.

Helpful to include

·The business problem, described as a workflow rather than as features
·Who uses it — staff, customers, or both — and roughly how many
·Systems it must connect to: accounting software, POS or payment hardware, ERP, spreadsheets
·Anything that already exists — a prototype, a legacy system, a manual process
·What has to be true for the first release to be worth shipping
·Your rough timing, and any fixed external deadline

What you get back

·A reply from an engineer within one business day
·A straight answer on whether this is work we are right for
·A short written architecture outline after the call
·A first-release scope, with what we would defer and why
·Relevant live software you can open and click through yourself
·No sales sequence, no drip campaign, no follow-up chasing

What happens after you write

Four steps, and the commercial conversation is the last of them — not the first.

01
We read it and reply
A real reply from an engineer within one business day, in English or Japanese. If your problem is outside what we do well, we say so in that first reply rather than booking a call to find out.
02
A 30-minute call
No deck, no discovery workshop. We ask about the workflow you want to change, the systems it has to talk to, and what has already been tried. You are talking to the people who would design the system.
03
A written architecture outline
After the call you get a short written summary: how we would structure the system, what belongs in the first release, what we would deliberately leave for later, and the open questions that still need answers.
04
Scope and sequencing
Only once the shape of the system is agreed do we talk commercials, phasing and timeline — against a defined scope rather than an open-ended estimate.

Whether we are the right company for this

We would rather tell you in the first email than three weeks into a proposal. Here is the honest split.

A good fit

·SMEs and mid-sized firms that want to own a real product at the end
·Operational software: accounting, retail, logistics, ticketing, field operations
·Work that touches physical hardware — POS terminals, payment devices, RFID and NFC, printers
·AI applied to a specific workflow with a measurable output, not a general chatbot
·Japanese firms needing bilingual product and support
·Teams with no in-house architect who need the system designed, not just coded

Not a good fit

·Staff augmentation — hiring developers by the month to sit in your team
·Hourly maintenance of a codebase we did not design
·Work priced purely on being the cheapest quote
·Projects that need the whole scope built before anything can ship
·Pure design, branding or marketing engagements

More on how we work and why: About Alienstacks.

Offices and company details

Alienstacks Co., Ltd. is registered in Thailand with operations in Japan. Visits to either office are by appointment — email us first so the right engineers are there.

HEAD OFFICE

Bang Na, Bangkok — Thailand

Registered office and engineering base. POS, IoT and application delivery for Thailand and Southeast Asia. Working language: English and Thai.

OPERATIONS

Tokyo — Japan

Product and client operations for our Japanese customers, whose firms number 200+ on our AI systems. Working language: 日本語 and English.

Legal nameAlienstacks Co., Ltd.
RegistrationDBD Reg. No. 0395569000469 (Thailand)
Emailcontact@alienstacks.com
Working languagesEnglish · 日本語
Response timeWithin one business day

Common questions before getting in touch

What is the fastest way to reach Alienstacks?

Email contact@alienstacks.com. It is the only inbox we use, it is read by the engineering side of the company, and it is the fastest route to a substantive answer. We reply within one business day.

Do you work in Japanese?

Yes. We have operations in Tokyo and our AI systems are used by 200+ Japanese firms, so calls, documentation and written scope can all be handled in Japanese as well as English.

Can we see the software before contacting you?

Yes, and we would prefer it. Public demonstrations of JP Accounting Suite, Virtual Office and CEO’s Cockpit run on fictional data and require no registration. Opening those first makes the first call much shorter.

Do you sign NDAs before a first conversation?

Yes, if you want one in place first. We can also hold the initial call at a level of detail that does not require it, and put an NDA in place before you share anything sensitive.

Which time zones do you cover?

Our working hours run across Southeast Asia and Japan, and we schedule deliberately into European and North American hours for clients in Germany, the United States and elsewhere.

Send the email.

A few paragraphs about the problem is all we need to give you a real answer. English or 日本語.

contact@alienstacks.com