Immutable audit trails, role based access, retention rules and evidence you can produce months later. In this sector, being able to prove what happened matters as much as the feature itself.
ACH, card payments, instant payments and the identity checks that go with them. Most agency pages in this market default to European regulation, which is little use to a firm operating in the States.
Our own delivery platform takes payments, splits them and pays out, every day. Payment edge cases are not theory to us: refunds, chargebacks, failed captures and reconciliation are all on our own balance sheet.
Financial software we develop
Work in this sector usually starts with one of these and grows once the compliance questions are settled and the first release survives a real month end.
Secure areas where clients see statements, documents, valuations and messages, with the access rules your compliance team needs and a login process that does not send half your clients to the phone line.
Applications that people actually finish: document upload, identity and sanctions checks through providers such as Persona, Alloy or Onfido, and a review queue for the cases that need a human decision.
Rate tables, eligibility rules and illustrations that produce the same answer every time and record which version of the rules produced it, because you will be asked about a quote from eight months ago.
Pipelines, tasks, reviews, document trails and renewal dates, built around how your advisers actually work rather than a generic CRM that everyone quietly keeps a spreadsheet beside.
Card payments, ACH and bank transfers, scheduled collections, split payouts and reconciliation, built on Stripe or the provider you already use, with card data kept inside the processor rather than your systems.
Account aggregation and verification through providers such as Plaid, so affordability checks and balance verification use live data rather than a customer typing numbers into a form.
The reports your regulator, your auditor and your board each want, generated from one source of truth so the numbers agree, with a record of who ran what and when.
Moving off a spreadsheet, an Access database or a system whose original developer has long gone, usually in stages that keep the business running rather than in one risky cutover weekend.
Who we build for
The regulation that applies to you shapes the build more than the label on your business does.
Client portals, review workflows, document trails and the reporting that keeps a compliance file complete without three people rekeying data.
Applications, affordability and eligibility rules, document collection, decisioning queues and the audit trail behind every decline.
Quotes, policy administration, renewals and claims intake, plus the portals that keep brokers and clients out of your inbox.
Client onboarding, engagement letters, secure document exchange and the recurring work that runs the practice.
A first product that can pass a security review, built so the compliance work does not have to be retrofitted before your first institutional client.
Security, compliance and the questions your auditor will ask
Financial software is judged on what you can prove. Our default build gives you role based access, an audit trail that records who saw or changed what and cannot be quietly edited, encryption in transit and at rest, multi factor authentication for staff, session controls, and retention rules that match your record keeping obligations rather than a developer preference.
If you take card payments, card data stays inside the payment processor and never touches your servers, which is the only sensible way to meet PCI DSS requirements without turning your own infrastructure into an audit problem. Where identity checks are in scope, we build the workflow around the customer due diligence rules your programme is written to, including FinCEN customer due diligence requirements for US firms, and we keep the evidence attached to the record rather than in a mailbox.
Account connections deserve their own decision. In the United States, consumer access to financial data is being formalised through the CFPB rule on personal financial data rights, which matters if you plan to pull bank data through an aggregator. We build to that direction of travel rather than to a European open banking model that does not apply where you operate.
Two honest boundaries. We are engineers, not your compliance advisers: we build to the rules your compliance function sets, and we will tell you when a requirement needs a specialist rather than a developer. And we are not a regulated entity, so we do not hold client money or act as a payment institution. Where a project needs that, we integrate the licensed provider you choose.
What we will do is make the security review straightforward. You get documentation of the data flows, where everything is hosted, which third parties are involved and what each one can see. Firms working toward SOC 2 or filling in a client security questionnaire usually find that most of the work is already written down.
The rails your money actually moves on
Most agency pages in this market describe European payment regulation. If you operate in the United States, these are the four that decide how your product behaves.
Fast, familiar and expensive, with chargeback risk attached. Right for one off and consumer payments. We keep card details inside the processor and design the retry and dispute handling properly, because failed payments quietly cost more than fees do.
Cheap and the backbone of recurring collections and payouts, but not instant and reversible under specific rules. The workflow has to show pending states honestly rather than pretending a transfer has settled when it has not.
Real time rails clear in seconds and are irreversible, which changes both the customer experience and the fraud thinking. Worth building for where speed genuinely matters, not simply because it is new.
Account verification, balance checks and transaction history through an aggregator, so affordability and onboarding decisions use live data. Consent and revocation need to be as carefully built as the connection itself.
How much does financial software cost?
An internal tool or client portal starts at about €15,000. A customer facing platform with payments, onboarding and multiple user types starts at about €40,000. A regulated firm website with real content work starts at about €7,500.
Only a minority of firms in this market publish any number at all. Ours are on the site, and they are honest starting points for real scope rather than a headline figure we discount later. Compliance work, security review support and integration with licensed providers are part of the quote, not a surprise line afterwards.
- How many user types and what each may see
- Identity checks, sanctions screening and review queues
- Payments: cards, ACH, scheduled collections, payouts
- Integrations with your existing systems and providers
- Evidence, reporting and support for a security review
Custom development is quoted on scope and is not discounted. Every rate we charge is published on our pricing page, including support after launch.
How a financial services project starts
Four steps. The first produces a written plan you keep whether or not you build with us.
-
01
Discovery and a compliance conversationWe map the workflow, the data and the rules that apply, with whoever owns compliance in the room. That conversation early is what stops a rebuild later.
-
02
Fixed scope and fixed priceScope, integrations, security work and reporting written down and priced. Changes are priced before they are built.
-
03
Build in two week slicesWorking software every fortnight, reviewed by the people who will use it and by whoever signs off risk, so approval is continuous rather than a cliff at the end.
-
04
Launch with the evidence packGo live with monitoring, audit logging and documentation of data flows, hosting and third parties, so your next client security questionnaire is mostly already answered.
What we tell financial firms before they commit
Three things that decide whether this money is well spent.
Buy the regulated pieces, build the difference
Do not build a payment institution, an identity provider or a core ledger if you can integrate a licensed one. Buy those, and spend your budget on the workflow that makes your firm different: how you assess a case, how you serve a client, how your advisers get through the week. That is the part no vendor sells you off the shelf.
Compliance costs more when it arrives late
Access control, audit trails, retention and evidence are cheap when designed in and expensive when retrofitted, usually under time pressure because a client security review is waiting. If you are heading toward SOC 2 or an institutional client, say so at discovery and the architecture will reflect it.
Our fintech proof is honest
We have built for a regulated advice firm, and we run our own platform that takes payments, splits them and pays out daily. We have not built a core banking system or a licensed payments product, and we would rather say that now than discover it together in month three. If you need a vendor with a shelf of bank logos, that is not us yet.
Regulated and money-moving work we have shipped
One regulated client, and one platform of our own where the payment edge cases are our problem.
Regulated financial advice explained as plainly as it is regulated, with enquiry forms built around what an adviser needs before the first call. Accurate, readable and defensible, which is the standard this sector is held to.
Our own platform, taking payments, splitting them between parties and paying out. Refunds, failed captures, disputes and reconciliation are daily operational reality rather than a slide in a pitch deck.
Financial software development FAQs
A client portal or internal tool starts at about €15,000, or $16,500 in the United States. A customer facing platform with payments and onboarding starts at about €40,000, or $44,000. A regulated firm website starts at about €7,500, or $8,250. You get a fixed scope and price after discovery, and every rate is published on our pricing page.
A focused portal or internal tool is typically three to four months. A customer facing platform with payments, identity checks and several user types is more often five to nine months. Third party providers set part of the timeline, because sandbox access and provider review take time we do not control.
Role based access, audit trails that cannot be edited, encryption in transit and at rest, multi factor authentication for staff, and retention rules matched to your obligations. We document data flows, hosting and every third party involved, so a security questionnaire or a SOC 2 readiness exercise starts from written facts rather than guesswork.
Card payments and payouts through Stripe, bank account connections through Plaid, and identity and sanctions checks through the provider you prefer, such as Persona, Alloy or Onfido. If you already have provider relationships we build to those rather than pushing our favourites, and we confirm what each one supports before we scope.
Yes. US projects usually need ACH for recurring collections and payouts, cards for convenience, and increasingly instant payment rails. Each has different timing, failure and reversal behaviour, and the workflow has to reflect that rather than pretending every payment settles the same way.
No on both. We are engineers. We build to the rules your compliance function sets, we integrate licensed providers where a regulated activity is involved, and we tell you when a question needs a compliance specialist rather than a developer.
You do. Repositories, cloud accounts, provider accounts and the data are in your name from day one rather than transferred at the end. If you move to another developer, they inherit a working project and full documentation.
Usually yes. Most projects involve a CRM, an accounting package, a policy or portfolio system, or a provider portal. We confirm in writing what each system exposes before committing to scope, because in this sector the gap between the sales sheet and the actual API is wide.
Buy when your process is standard and a product fits, because you will be live sooner and cheaper. Build when the process is your competitive edge, when per seat licence costs stop making sense at your size, or when the product cannot bend to a rule you are required to follow. We give you that answer at discovery, before budget is committed.
Yes, at published monthly rates. Updates, security patching, monitoring, dependency upgrades and small changes are covered, with larger pieces quoted separately. In this sector the patching matters more than most: an unpatched dependency is the finding that turns a routine review into a problem.
Frequently. We start with a codebase audit at a fixed price, which tells you the real condition of what you own, the security and dependency risks, and a costed plan. Sometimes the honest answer is that it is fine and needs maintaining rather than replacing.
That is usually part of the work. You get documented data flows, a third party inventory, access control and logging you can demonstrate, and answers written in the language a reviewer expects. It is far cheaper to build this way than to assemble it under deadline when a large client asks.
Have a financial services project in mind?
Tell us the workflow, the rules that apply and the systems you already run. You will get a plain answer on approach, timeline and price, and an honest view on what to buy rather than build.