Brooklyn, 11211, NY,
United States
Working Not Working Technographics
Working Not Working Technographics, Software Purchases, AI and Digital Transformation Initiatives
Discover the latest software purchases and digital transformation initiatives being undertaken by Working Not Working and its business and technology executives. Each quarter our research team identifies on-prem and cloud applications that are being used by the 2000 Working Not Working employees from the public (Press Releases, Customer References, Testimonials, Case Studies and Success Stories) and proprietary sources.
During our research, we have identified that Working Not Working has purchased the following applications: Stripe Payments for Payment Processing in 2019, Ruby Live Chat for Chatbots and Conversational AI in 2021, Google Workspace (Formerly Google G-Suite) for Collaboration in 2013 and the related IT decision-makers and key stakeholders.
Our database provides customer insight and contextual information on which enterprise applications and software systems Working Not Working is running and its propensity to invest more and deepen its relationship with Stripe , Ruby , Google or identify new suppliers as part of their overall Digital and IT transformation projects to stay competitive, fend off threats from disruptive forces, or comply with internal mandates to improve overall enterprise efficiency.
We have been analyzing Working Not Working revenues, which have grown to $220.0 million in 2024, plus its IT budget and roadmap, cloud software purchases, aggregating massive amounts of data points that form the basis of our forecast assumptions for Working Not Working intention to invest in emerging technologies such as AI, Machine Learning, IoT, Blockchain, Autonomous Database or in cloud-based ERP, HCM, CRM, EPM, Procurement or Treasury applications.
Working Not Working Tech Stack and Enterprise Applications
Working Not Working ERP
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| Stripe | Legacy | Stripe Payments | Payment Processing | ERP | n/a | 2019 | 2019 |
In 2019, Working Not Working deployed Stripe Payments to handle online card acceptance and client billing on its public website. Stripe Payments was implemented as the company's Payment Processing layer to centralize acceptance of credit and debit transactions for customer invoices and site-based purchases.
The implementation focused on embedding Stripe Payments into checkout and invoicing flows, leveraging gateway and tokenization capabilities to reduce card data exposure. Engineering implemented client-side tokenization and server-side capture patterns, and configured Stripe event webhooks to surface payment events into internal operational workflows.
Operational ownership for Stripe Payments resides with payments operations and finance teams, with engineering maintaining the website integration and webhook handling. The deployment positioned Stripe Payments to support client billing, transaction settlement orchestration, and dispute handling as the primary Payment Processing capability for the site.
|
Working Not Working AI-Powered Application
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| Ruby | Legacy | Ruby Live Chat | Chatbots and Conversational AI | AI-Powered Application | n/a | 2021 | 2021 |
In 2021, Working Not Working implemented Ruby Live Chat on their public website, deploying Ruby Live Chat as a Chatbots and Conversational AI solution to enable real-time conversational engagement with site visitors. The deployment surface is a web-embedded chat widget providing real-time messaging, session persistence, automated conversational prompts, and human agent handoff capabilities that are characteristic of Chatbots and Conversational AI platforms.
The implementation is scoped to website-driven client and talent interactions and is administered by site operations and community management teams, aligning conversational workflows with customer engagement and talent outreach functions. Configuration emphasizes availability-based routing and escalation into human operator flows, with conversation transcripts and logging used for operational tracking and moderation.
|
Working Not Working Collaboration
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
| Legacy | Google Workspace (Formerly Google G-Suite) | Collaboration | Collaboration | n/a | 2013 | 2013 |
Working Not Working implemented Google Workspace (Formerly Google G-Suite) in 2013. The 2013 deployment established a centralized cloud tenant delivering Collaboration capabilities including Gmail, Calendar, Drive, Docs, Sheets, Slides, and Google Meet across the United States-based professional services firm with approximately 2,000 employees, and the implementation is referenced on the company website.
The deployment focused on core Collaboration modules, with configuration performed through the Google Admin console to provision the corporate domain, user accounts, group-based access controls, and shared drives for creative and account teams. Standard configuration elements included mail routing and retention policies, collaborative document workflows in Google Docs and Sheets, and scheduled meeting and conferencing workflows via Google Meet.
Operational coverage extended across creative, recruiting, account management, and back-office functions, positioning Google Workspace (Formerly Google G-Suite) as the primary Collaboration platform for internal communication, file sharing, and synchronous and asynchronous teamwork. Governance practices aligned with typical cloud collaboration administration, using role-based administration, group provisioning, and device management controls to enforce access and policy across the organization.
Rollout and ongoing governance emphasized centralized administration through the Google Admin console and group policy enforcement for workspace collaboration, with site and departmental adoption managed through centralized account provisioning and shared drive structures. The implementation narrative centers on Google Workspace (Formerly Google G-Suite) as the enterprise Collaboration backbone for Working Not Working.
|
Working Not Working CRM
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
|
|
|
|
Customer Experience | CRM |
|
2017 | 2017 |
|
|
|
|
|
Customer Support | CRM |
|
2015 | 2015 |
|
|
|
|
|
Sales Automation, CRM, Sales Engagement | CRM |
|
2021 | 2021 |
|
Working Not Working PaaS
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
|
|
|
|
Transactional Email | PaaS |
|
2014 | 2014 |
|
|
|
|
|
Transactional Email | PaaS |
|
2015 | 2015 |
|
Working Not Working IaaS
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
|---|---|---|---|---|---|---|---|---|
|
|
|
|
Application Hosting and Computing Services | IaaS |
|
2015 | 2015 |
|
|
|
|
|
Content Delivery Network | IaaS |
|
2019 | 2019 |
|
IT Decision Makers and Key Stakeholders at Working Not Working
| First Name | Last Name | Title | Function | Department | Phone | |
|---|---|---|---|---|---|---|
| No data found | ||||||
Apps Being Evaluated by Working Not Working Executives
| Date | Company | Status | Vendor | Product | Category | Market |
|---|---|---|---|---|---|---|
| No data found | ||||||