Peter Millington

Peter Millington

CEO

Anne Millington

Anne Millington

Chief Administrative Officer

Chris Twyman

Chris Twyman

CMO

George Kastner

George Kastner

Strategic Advisor

Marc Lowenthal

Marc Lowenthal

Product Advisor

Parker Johnson

Parker Johnson

Sr. Software Engineer

Koi Stephanos

Koi Stephanos

Sr. Data Scientist

John Caspers

John Caspers

Sr. Software Engineer

Mete Pete

Our team has been designed to deploy our solutions in the most efficient way:

  • 01

    Discovery

    Discovery process. Interview and gather data from Client's team and chosen department as designated by Client and to formulate a full specification for a Statement of Work (SOW).

    • Specification and Company Analysis
    • Technical Integration
    • Data Feed Analysis
    • Implementation Analysis
    • Application integration
  • 02

    Migration strategy

    Each SOW will include a full project plan with all dependencies and risks identified.

  • 03

    Implementation

    SFS will allocate a dedicated project manager that will manage the both client and SFS implementation team. We include some of our development team as part of every implementation to expose them to real client interaction and feedback.

  • 04

    Support

    Our support program gives you, our customers the security that we are with you when you need us most.

    Severity

    Response

    A Severity 1 incident is defined as one that produces an emergency situation in which the Covered Software is substantially or completely non-functional or inoperable.

    In the case of a Severity 1 incident, a qualified member of SFS’s staff will respond via telephone to begin to diagnose the problem within one (1) hour.

    A Severity 2 incident is defined as one that produces a detrimental situation in which the Covered Software is usable, but materially incomplete; performance (throughput or response) of the Covered Software degrades substantially such that there is a severe impact on use under reasonable loads; one or more mainline functions or commands is inoperable; or the use is otherwise significantly impacted.

    In the case of a Severity 2 incident, a qualified member of Company’s staff will respond by telephone or email as soon as reasonably possible, but in any event a response will be provided within eight (8) hours.

    A Severity 3 incident is defined as one that produces an inconvenient situation in which the Covered Software is usable but does not provide a function in the most convenient or expeditious manner, but the user suffers little or no significant impact.

    Company will exercise commercially reasonable efforts to resolve Severity 3 problems in future maintenance releases.

How we match up: