Circle ICT — Systems, Platforms & Practical Technology
LoginRegister
CIRCLE ICTINFORMATION & COMMUNICATIONS TECHNOLOGY Talk to an ICT Adviser
I need help with… Solutions View All Solutions Enterprise Systems Management Portals Circle® Arc™ WMS Circle® Forums Circle Games — Free-to-Play Circle Games — Age-Restricted Games Lot Purchasing Products Certified Refurbished Computers Services Professional Operations Assessment Training & Learning Sessions Talks & Speaking Engagements Why Circle ICT Company Our History Our Principles Intellectual Property Contact Login Sign Up
HOW WE BUILD

Technology should solve problems.
Not create new ones.

These principles guide how Circle ICT designs products, works with clients, prices services and supports technology after deployment.

01

Business problems before technology.

We start with the operation, not the software. Technology should exist because it makes work clearer, faster, more reliable or more accountable—not simply because a new system can be built.

02

Technology without artificial lock-in.

We do not believe a client should stay because leaving is intentionally difficult. A client should stay because the technology and service continue to create value.

03

Know what you're paying for.

Pricing, one-time charges, recurring services, renewal dates and major upgrade policies should be understandable before a client commits. We distinguish clearly between a software license and an ongoing managed service.

04

Clients remain in control.

Where a service is cancellable, the client should be able to cancel it without being trapped in a sales conversation. Purchases, active services, invoices, renewal dates and service status should remain visible to the client.

05

Software should create continuity.

A good system should preserve institutional knowledge instead of allowing it to disappear when employees, officers or leadership change. Technology should help an organization remember.

06

Build for the work that actually happens.

We design around real workflows, responsibilities and decisions. Features should serve the organization using them—not force the organization to reorganize itself around unnecessary software complexity.

OUR COMMITMENT

Clear before purchase. Clear after deployment.

Clear pricing

Know what is one-time and what is recurring.

Visible renewals

Know when a service renews and what it costs.

Clear ownership

Know what license, version or service you purchased.

Transparent upgrades

Know what is included and what is an optional future purchase.

Accessible records

See purchases, invoices and active services in your Client Panel.

Freedom to leave

Eligible recurring services can be cancelled without artificial barriers.

“A customer should not have to stay because leaving is difficult. They should stay because the service continues to create value.”

— A Circle ICT operating principle