cto: client use case - op
TRANSCRIPT
OP Use Case
Use Case: a CTO client study
OP: a funded internet start-up
The primary OP business system is a large complex website
CTO were engaged to provide expert advice, manage the build, and run all the
company technical infrastructure
OP – full name withheld due to an NDA
How CTO helped
Requirements gathering, documentation and specification: business system functionality
and business processes engineering
Tender process management: find the perfect web development company
for the type of project
Project planning and management: build schedules, budget planning, test planning, management reporting
Architecture authority: quality control and quality assurance for the design of the
business system (built by web development company)
Business process systems design, commission, configuration and integration: document
management systems, email, CRM, security, backup and redundancy etc
Operational management: systems issue management, 3rd party SLA management, system monitoring, advice, configuration
The architecture
Design principles
Everything as a service – In the cloud
Low (human) touch business flows
Security and redundancy as a priority
Everything as a service
Bespoke built systems: business website, disaster recovery system, test/demo
system, content management system all hosted and backup using a cloud hosting
company
Software as a service SaaS: email, document management, customer
relationship management, marketing, issue management systems all commissioned from
trusted vendors as a service e.g. company domain gmail
Platform and Infrastructure as a Service PaaS/IaaS: firewall - network
and website security and redundancy, system monitoring and analytics, website payment platform, data backups, remote desktop e.g.
data backups to Amazon Web Services
Exceptions: accountancy software and middleware data flow management software
are ‘in-house’ bought software – to make them ‘cloud’ CTO install and run them on a remote desktop so that they are seen as a
‘cloud’ like services to the client
Low touch business flows
Data Integration: CTO configure and manage middleware data integration
software which…
Extracts customer information from the website an feeds it automatically to the CRM
system and the accountancy system…
Extracts payments from the website and feeds them into the accountancy system…
Feeds customer raised issues from the website or email to an issue management
system.
Payment System APIs: the business website uses trusted payment platforms for customer payment details and processing –
the website uses the payment system APIs for instant processing
Integrated SaaS: CRM system and marketing systems chosen due to their compatibility and automatic integration
Security and redundancy as a priority
Security: website firewall – encrypted connections, browser checks, IP checks, malware checks, denial of service attack
defence etc
Security: password management by CTO by running all your SaaS accounts, configuring and monitoring the servers and employing strong secure and safely stored encrypted
passwords
Security: all customer payment details are stored and processed by an accredited
payment platform and not managed by OP or CTO e.g. paypal
Redundancy: mirror disaster recovery website system – synchronised, and at a
separate location
Redundancy: data backed up by webhost, data also backed up via middleware to
Amazon Web Services (AWS) for archive e.g. fast recovery and slow recovery
Redundancy: daily accountancy interface files stored at AWS for full back-
up and recovery of accountancy data
Redundancy concerns: currently trusting the SaaS providers of the email,
document management, issue management and CRM systems to safely manage the
redundancy of the data
OP run a fully functioning business and do not own or run any hardware or
software – outside of employee laptops with the basic apple or windows
operating systems
Can CTO help? Contact CTO for a free consultation.
tel: 0044 (0)20 3478 9049