Software for regulated industries - and the domain expertise we won't fake.
Intention InfoService has real, published web builds - including a professional-training platform and a financial-services site - but not a client portfolio in every regulated sector below, and we will not fake the ones we lack. What a regulated vertical actually demands is not a logo wall anyway - it is knowing exactly which legal obligation binds you and which never touches us, building the machinery so you can meet the one that is yours, and declining the role or the badge that carries the liability. Each guide below does that for its sector in the open, including the parts that cost us the sale. What we'll actually do for you lives on the services pages; what we build it with, and how we choose, lives on the technologies pages. This page is who each obligation belongs to, and the roles we won't take.
- We name whose obligation each one is
- We name the roles we won't take
- No borrowed logos or case studies
Sector expertise is the easiest thing in this business to fake. Here's how to tell ours is real.
We have real builds you can see on our work page, but not a client in every sector below - no healthcare logos, no "trusted by", no years-in-fintech to quote - and we won't fake the ones we lack. A wall of marques is the cheapest thing an agency can assemble and the hardest thing you can verify, so it proves almost nothing about the one thing that matters here: whether a team understands the sector, or just redecorated a generic pitch with its vocabulary. The checkable tell is the opposite of a logo. Each guide below does things a firm faking domain expertise would never publish, because every one costs the writer a sale. It names which legal obligation binds you and which never touches us - which forfeits the "compliant vendor" badge language competitors lean on. It builds the machinery so you can meet the obligation that is genuinely yours, instead of asserting an outcome no software can own. And it names the most profitable thing it could dishonestly sell in that sector - the role that carries the liability, or a compliance badge no software can wear - and turns it down. Below is one line from each guide you can check for yourself.
The EdTech guide would rather point a training company at Moodle, Canvas or Open edX and turn the engagement down than sell it a custom LMS it doesn't need.
The healthcare guide says in writing that if a build genuinely needs us to hold your patients' data or sign a business associate agreement, we are not your vendor - rather than take the work and quietly become one.
Our FinTech guide turns down crypto exchanges, wallets and core-banking ledgers outright, and flags when the real project is a money-transmitter licence for your counsel, not a screen we design.
The real-estate guide refuses to build the two products where the liability actually concentrates - the automated tenant approve-or-decline, and the valuation the market acts on.
The travel guide won't become your seller of travel or your package organiser of record, and won't hold the traveller's money - it builds the booking engine and flags the feature that could quietly change what you legally are.
Our media guide refuses to be your licensing counterparty, your royalty payer or your host of record, because that legal role doesn't transfer, and anyone who says it does is selling you something that isn't real.
A firm that only rented the logos could not write any of this, because every line of it hands back a sale we could have closed. We can, because in a sector where we have no portfolio to wave, telling you exactly where our responsibility ends is the only proof worth anything - and it is the proof a logo wall is built to avoid.
Each sector, written up in depth
Each guide names the obligations that shape the build, the machinery we'd build so you can meet them, and the point at which we'd tell you to configure something off the shelf instead.
EdTech & LMS
Custom LMS, learning platforms and student portals, built on open standards like LTI, SCORM and xAPI.
See who FERPA and COPPA really bind, and when extending Moodle beats buildingHealthcare & Patient Portals
Patient and provider portals built on FHIR and SMART on FHIR, architected so patient data stays on your side.
Why we stay on the outside of the business-associate line, and never store your PHIFinTech & Payments
Embedded-payment front ends, financial dashboards and back-office tooling, built on payment processors and open-banking rails.
You're almost never the bank - see how the ledger proves where the money wentReal Estate & Listing Portals
Listing portals, property search and agent CRM, built on the RESO Web API and IDX.
How a neutral-looking filter becomes a fair-housing decision, and the two builds we refuseTravel & Hospitality
Booking engines, reservation systems and hotel platforms, built to the open standards travel runs on - NDC and OpenTravel.
A booking is a promise someone else keeps, and one feature can change what you areEntertainment & Media
Streaming, publishing, community and ticketing platforms, with the rights, moderation and paywall machinery built into the software.
Every item needs a provable licence and a lawful way out - here are the roles we refuseWhat every one of these guides does
These sectors could not look more different, and the method underneath them is identical. It is the method, not a portfolio, that carries the expertise.
It allocates the obligation
It names which legal duty binds you and which binds a school, a bank, a broker, a carrier or a rightsholder instead - and which never reaches us at all. Getting that right forfeits the "compliant vendor" badge language, which is exactly why so few pages publish it.
It builds the machinery, not a claim
Every "this obligation is yours" is paired with "and here is what we build so you can meet it" - the access model, the ledger, the consent capture, the takedown pipeline. We never call the result compliant, secure or accessible, because those are properties of how you operate, not of software we hand over.
It declines the profitable dishonest sale
In most of these sectors that is a role that carries the risk - the business associate, the money mover, the tenant-screening decision of record, the seller of travel, the licensing counterparty - which stays yours whatever a contract says, so we name it and leave it with you. In edtech, where the law never reaches us, it is the "FERPA-compliant vendor" badge and the custom platform a school does not need. Each guide names its version and turns it down.
It shows no portfolio it doesn't have
No invented case studies, no borrowed logos, no years-in-sector. Each guide bridges the same two real web projects as a problem shape, names precisely where that shape stops matching the sector, and fences off what we have not shipped.
You won't find a client logo wall on this page
That is deliberate. We have no clients in these sectors, and we will not rent the logos, borrow a case study, or claim experience we do not have - the row of marques an "industries we serve" page usually leads with is the cheapest thing in this business to assemble and the hardest thing for you to verify. Where a real credential does exist in a sector - a certification, a partner programme, an accreditation - the guide for that sector names it precisely, says plainly that we do not hold it, and corrects the category errors competitors commit by implying they do. What we offer instead of a logo wall is on every guide: the obligation named correctly, the machinery to meet it, the liability role refused, code and data you own outright, and a paid discovery before any price.
See how it all fits together
Services
What we'll actually do across every sector: design, build, market and maintain.
See the eight things we doTechnologies
What we build each of these on, and how we choose - every guide says when not to use it.
See the stacks, and how we pickPricing
The scope sets the price, not the sector. Published starting prices for websites, software and more.
See what things start atOur work
The two projects we've actually shipped, described honestly and never dressed up as sector work.
See the two we shippedBuilding for a regulated sector, answered
You list these industries but say you have no clients in them - so what does 'industry expertise' mean here?
It means something narrower and more checkable than a case-study wall. It is knowing exactly which legal obligation binds you and which binds someone else, building the software machinery so you can meet the one that is yours, and declining the most profitable thing we could dishonestly sell in each sector - the liability-bearing role, or a compliance badge no software can wear. All of that is something a firm faking domain knowledge would never put in writing, because each part forfeits a badge or a sale, which is precisely why it is worth more to you than a logo. Each guide does it in the open, and you can check it on the page.
Why won't you show logos or case studies from these sectors, like other agencies do?
Because we have none, and we will not fabricate or borrow them. A logo is the easiest thing to assemble and the hardest thing for you to verify, and it says nothing about whether a team understands a sector's obligations or just learned its vocabulary. We would rather show you the two projects we have actually shipped, tell you exactly where their shape stops matching your sector, and let the depth of each guide stand where a portfolio we do not have would otherwise go.
Do I have to be in one of these sectors to work with you, and what if mine isn't here?
These are the sectors we have written up in depth because they are the ones where getting the allocation wrong is most expensive, not the limit of what we build. The method is the same wherever you are: name whose obligation each duty is, build the machinery to meet yours, and decline the role or the badge that carries the risk. Tell us your sector and we will apply it, and if yours has a regulatory shape we genuinely should not be touching, we will say so on the first call rather than learn it on your budget.
What does 'refuse the liability-bearing role' mean - aren't you just offloading risk onto me?
No. In most of these sectors there is a role - the business associate that holds the data, the money mover, the tenant-screening decision of record, the seller of travel, the licensing counterparty - that carries the legal liability, and it is usually the stickiest thing a vendor can grow into. The point is that the liability stays with you whatever a contract says; a vendor who offers to absorb it is selling a comfort that is not real. We build the machinery around that role and leave the role where the law already puts it, which keeps your risk from expanding onto a party you cannot audit.
Why does every industry guide tell me when NOT to build, or to buy something off the shelf?
Because the most expensive thing we could sell you is a custom build you did not need. Every guide carries a section that names when a configured platform beats a bespoke one, and turns the work down when that is the honest answer. In a sector where we cannot point to a portfolio, talking you out of the wrong build is the only credential worth anything before the first right one ships.
How does a project in a regulated sector actually start, and how do you price it?
It starts with a paid discovery - never a number invented before anyone has mapped where your data, your money and your obligations actually flow - which ends in a written scope and a fixed price, credited toward the build. There is no price table on an industry page on purpose: the sector does not set the price, the scope does, and published starting prices live on the pricing page. An NDA is available before you tell us anything, and if discovery finds the honest answer is a configured platform or a role we will not take, we say so before you spend.
Building something a regulated sector will judge?
Tell us what you're building. We'll name whose obligation is whose, build the machinery you need to meet yours, and tell you the roles to keep with your counsel rather than hand to a vendor - including when the honest answer is to configure something off the shelf.