21:I[64418,["2399","static/chunks/53c0104b-0bf61919c7da6d97.js","8500","static/chunks/8500-5231dcda86e70456.js","8815","static/chunks/8815-a3d30cde6722147a.js","7317","static/chunks/7317-e53b91f569d5aae3.js","1760","static/chunks/1760-823e5ede79a02405.js","8454","static/chunks/app/journal/%5Bslug%5D/page-978ee4012cc7c4c6.js"],"default"] 22:I[60423,["2399","static/chunks/53c0104b-0bf61919c7da6d97.js","8500","static/chunks/8500-5231dcda86e70456.js","8815","static/chunks/8815-a3d30cde6722147a.js","7317","static/chunks/7317-e53b91f569d5aae3.js","1760","static/chunks/1760-823e5ede79a02405.js","8454","static/chunks/app/journal/%5Bslug%5D/page-978ee4012cc7c4c6.js"],"default"] 23:Tc17,

SaaSで爆速開発して業務変革、なんて言うのは簡単だけど、現実はどうもそう甘くないらしい。

転職して現職に来てから、SaaSのローコード・ノーコード環境に触れている。開発自体は多少経験している程度だけど、プロジェクトとしては複数のプロダクトで様々やっている。
やってみて率直に思うのは、OOTB（Out Of The Box：標準機能）に準拠してクイックな開発ができれば、間違いなく恩恵は受けられるんだろうなということ。

でも、実際の現場はそう簡単じゃない。
業務部門からは「今のやり方を変えたくない」という現状踏襲の要望が出るし、謎のこだわりによってOOTBから外れたカスタマイズを求められることも多い。

それに、海外製のツール特有の違和感もある。
日本語の表示が崩れるのもそうだし、ワークフローの考え方がそもそも日本の文化と合わないのか、現場で「使いやすい！」となりにくい。
パッケージ環境だからこその隠れ仕様や制限も多くて、意図した挙動にならずに躓くポイントが実はたくさんあるような気がしている。

結局、SaaSで爆速開発を進めるには、IT部門と業務部門が同じ方向を向いていることや、OOTBに合わせるという強い前提が必要なんだと思う。

JTCと呼ばれる企業もDXやAXを進めようと頑張っていることは、イベントや企業団体などで交流することなどからよくわかる。
だけど、極端にセキュリティやガバナンスを意識しすぎたり、IT部門と業務部門の関係性が従来通りだったりする。
強いトップダウンのリーダーがいなかったり、自社でやらずに何でも外注する文化が根強かったりして、SaaS開発と業務変革を同時に進めるのは本当に難しいなと思う。このあたりは世代間の感覚の違いもあるのかもしれない。

グローバルで評価の高いSaaSを入れたところで、活かせるかどうか、ROIを出せるかどうかは本当に複合的な要素で決まる。

もし外資のSaaSやパブリッククラウドを入れまくって、結局活かしきれない状態が続けばどうなるか。
JTCが本業で稼いだ売上が、米国企業の収益になり、ただの「間接的な送金システム」として機能してしまう。正直、この構図を変えるのは相当難しいと思う。

だからこそ、良いものを活かしきる姿勢で製品選定をして活用することが重要なんだと意識しながら日々の業務と向き合っている。

まとまりのない文章だけど、転職してからずっと思っていたこのモヤモヤは、最近のAI導入の文脈でもそっくりそのまま当てはまるなと感じて、ふと書き出してみた。

24:Tafe,

It's easy to talk about fast development and business transformation with SaaS, but reality isn't that simple.

Since changing jobs and coming to my current company, I've been exposed to SaaS low-code and no-code environments. While my own hands-on development experience is somewhat limited, I've been involved in a variety of projects across multiple products.
What I frankly feel after trying it is that if we can develop quickly while sticking to OOTB (Out Of The Box), we can definitely reap the benefits.

However, the actual field is not that easy.
Business departments often request to "keep the current way of doing things," and a mysterious obsession often leads to demands for customization that deviates from OOTB.

Then there is the unique awkwardness of foreign-made tools.
Japanese displays get messed up, and perhaps the workflow concepts just fundamentally clash with Japanese culture, making it hard to be praised as "easy to use" in the field.
Because it's a packaged environment, there are many hidden specs and limitations, and I feel there are actually many stumbling blocks where things don't behave as intended.

Ultimately, to advance rapid development with SaaS, I think strong prerequisites are needed: the IT and business departments pointing in the same direction, and a commitment to adapting to OOTB.

I know that so-called JTCs (Traditional Japanese Companies) are also trying hard to promote DX and AX, which is clear through interactions at events and corporate associations.
But they often overly prioritize security and governance, and the relationship between IT and business departments remains unchanged.
Without a strong top-down leader, and with a deep-rooted culture of outsourcing everything instead of doing it in-house, it's genuinely hard to advance SaaS development and business transformation simultaneously. Generational differences in sensibilities might also play a part here.

Even if you introduce a globally highly-rated SaaS, whether you can utilize it and generate ROI truly depends on complex factors.

What happens if you excessively introduce foreign SaaS and public clouds but fail to fully utilize them?
The original earnings made by JTCs just become revenue for US companies, functioning simply as an "indirect remittance system." Honestly, I think it's quite difficult to change this structure.

That's exactly why I try to face my daily work with the mindset that it's important to select products with a posture of maximizing what is good, and to utilize them well.

It's a rambling piece, but I suddenly felt the urge to write this down because I feel this exact same frustration—which I've had since I changed jobs—applies perfectly to the context of recent AI adoption.

8:["$","article",null,{"className":"min-h-screen bg-background pb-32 text-foreground transition-colors duration-300","children":[["$","script",null,{"type":"application/ld+json","dangerouslySetInnerHTML":{"__html":"{\"@context\":\"https://schema.org\",\"@type\":\"BlogPosting\",\"headline\":\"Thoughts on SaaS Low-code Development and the \\\"Indirect Remittance System\\\"\",\"inLanguage\":\"en\",\"datePublished\":\"2026-04-09T14:28:53.516Z\",\"dateModified\":\"2026-04-09T14:28:53.516Z\",\"image\":[],\"author\":{\"@type\":\"Person\",\"name\":\"fson\",\"url\":\"https://fsonhub.com/career\"},\"publisher\":{\"@type\":\"Organization\",\"name\":\"fsonhub\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https://assets.fsonhub.com/fsonicon.png\"}},\"mainEntityOfPage\":{\"@type\":\"WebPage\",\"@id\":\"https://fsonhub.com/journal/saas-low-code-and-remittance-system\"}}"}}],["$","$L21",null,{"en":"Thoughts on SaaS Low-code Development and the \"Indirect Remittance System\"","ja":"SaaSのローコード開発と「間接的な送金システム」について思うこと"}],["$","nav",null,{"className":"fixed inset-x-0 top-0 z-50 border-b border-usu bg-background/85 backdrop-blur-md dark:border-usu-dark","children":["$","div",null,{"className":"px-6","children":["$","div",null,{"className":"mx-auto flex h-14 max-w-5xl items-center justify-between","children":[["$","$L6",null,{"href":"/","aria-label":"fsonhub Home","className":"$undefined","children":["$","div",null,{"className":"flex items-baseline text-sumi dark:text-sumi-dark transition-colors duration-300","children":[["$","span",null,{"className":"font-display text-xl font-medium leading-none tracking-tight","children":"fson"}],["$","span",null,{"className":"font-body text-xl font-normal leading-none tracking-tight opacity-50","children":"/hub"}]]}]}],["$","$L6",null,{"href":"/journal","className":"u-label uppercase transition-colors hover:text-ai dark:hover:text-ai-dark","children":["← ",["$","$L7",null,{"en":"Back to Journal","ja":"ジャーナルに戻る"}]]}]]}]}]}],["$","main",null,{"className":"px-6 pt-32 sm:pt-40","children":["$","div",null,{"className":"mx-auto max-w-5xl","children":["$","div",null,{"className":"grid gap-4 md:grid-cols-12 md:gap-8","children":[["$","div",null,{"className":"flex gap-4 md:col-span-3 md:flex-col md:gap-1","children":[["$","time",null,{"lang":"en","dateTime":"2026-04-09T14:28:53.516Z","className":"u-label","children":"2026.04.09"}],["$","$L6",null,{"lang":"en","href":"/journal/category/Tech","className":"u-label uppercase transition-colors hover:text-ai dark:hover:text-ai-dark","children":"Tech"}]]}],["$","div",null,{"className":"min-w-0 md:col-span-9","children":[["$","$L22",null,{"titleJa":"SaaSのローコード開発と「間接的な送金システム」について思うこと","contentJa":"$23","titleEn":"Thoughts on SaaS Low-code Development and the \"Indirect Remittance System\"","contentEn":"$24","tocJa":[],"tocEn":[]}],"$L25","$L26","$L27","$L28"]}]]}]}]}]]}]