Two-sided product
Investor activity and broker/dealer administration relied on shared accounts, products, and transaction context.
Anonymous financial technology case study
Extending a multi-asset trading platform across investor and broker workflows
A trading technology provider needed product engineering across investor-facing trading and broker/dealer back-office workflows for multiple asset classes.
The situation
One trading platform served two user groups with different but tightly connected responsibilities.
Individual investors used client applications for stock and futures activity, while brokers and dealers managed accounts, products, reporting, and risk in the back office.
New functions had to integrate specialist financial APIs, messaging protocols, and charting components while established product workflows still needed maintenance and support.
The challenge
Evolve investor and professional workflows together without separating trading from control and risk.
The platform had to connect user experience, financial messaging, back-office control, and quality engineering.
Specialist integration
Financial APIs, FIX messaging, charting, and installation components introduced distinct dependencies.
Product support
Maintenance and issue resolution had to accompany delivery of new capabilities.
The solution
A cross-functional engineering and QA team extended desktop, web, connectivity, and back-office functions together.
Product work included integration, new features, testing, support, and maintenance across the trading environment.
- 01
Connect financial messaging
Use WCF and QuickFIX components for specialist connectivity and message exchange.
- 02
Extend user workflows
Develop C#, C++, ASP.NET, and Windows Forms capabilities for investor and professional users.
- 03
Test and support delivery
Apply NUnit, logging, charting, and installer tooling while keeping product support inside the delivery model.
How the work was structured
The team worked across the trading path rather than treating each interface as a separate product.
Investor orders, broker/dealer controls, account information, products, reporting, and risk shared common platform dependencies.
Connectivity work was reviewed alongside desktop and web behavior so protocol changes did not become isolated integration tasks.
Engineering and QA supported both new product work and the maintenance needs of existing users.
01Order
Support investor trading activity.
02Connect
Exchange financial messages.
03Control
Manage accounts and products.
04Review
Use reports, tests, and risk checks.
The result
The platform gained broader engineering capacity across investor, broker, reporting, and risk workflows.
The documented engagement expanded connected product functions while keeping maintenance and support inside the same delivery model.
Two-sided coverageacross investor and broker/dealer users
Multi-asset workflowssupporting stocks and futures
Delivery capacityfor integration, features, testing, and support
Product functions stayed connected
Accounts, products, trading, reporting, and risk were extended within one environment.
Specialist protocols were integrated
Financial messaging became part of the product workflow and test process.
Support accompanied development
User needs remained inside the same product-engineering model.
Case taxonomy
Searchable by industry, technology, product, and business need.
Industry and product
- Financial Services
- Capital Markets
- Trading Platform
- Broker-dealer Software
Technology and delivery
- C#
- C++
- ASP.NET
- Windows Forms
- WCF
- QuickFIX
- NUnit
Business need
- API Integration
- FIX Messaging
- Account Management
- Risk Management
- Product Support
Extend trading workflows without fragmenting the platform
Need engineering capacity across trading, back-office, and integration work?
Get in touch
Ready to build software that fits your business?
Tell us what you need to build, modernize, automate, or augment with AI. We can start with a focused discussion or a no-risk 1-week trial.
“A fantastic company to work with.” After the initial rapid development project, American Shipping Co. kept two Shinetech developers embedded for nearly four years, supporting internal and external tools and new AI initiatives.
CEO, American Shipping Co. - 5-star Google Review