10 web platforms, 2 mobile apps, 27 automations — in 75 days.

On February 12, 2026, I installed Viktor into our Slack workspace. At the time, CollabED ran on a patchwork of disconnected platforms. Our community lived on Group.app, which limited the number of moderators I could assign and charged a premium for features we were outgrowing. Volunteer onboarding was manual. Check-in emails went out when I remembered to send them. Our social media presence depended entirely on whether I had time that week.

I was working full time on top of running the nonprofit. Information, communication, and workflows were spread across too many places to maintain visibility.

My first request to Viktor that day was a grant research task. Within hours, I asked for help building an organizational chart. I had been struggling to create something functional in traditional tools. When Viktor generated the org chart, it did not look like a static document. It looked and functioned more like a living webpage. That was the turning point. I immediately thought about my experience working for a large organization that had an internal platform connecting people, roles, and workflows in one place. That is how CollabNET was born.

I had explored hiring freelance developers, but the cost was prohibitive for a nonprofit with no revenue. I had tried building things myself in no-code platforms, but nothing connected. Every solution solved one problem and created two more. Viktor was originally installed as a Slack integration. I expected it to help with messages and maybe some research.

What I discovered was something closer to a coworker who could build, ship, and maintain the systems I described.

The first two weeks moved fast. On February 13, Viktor built a ticketing system inside CollabNET so volunteers could submit help requests routed to the right department. By February 21, we had a content submission portal and a social media submissions portal, both built in a single session.

On February 28, I told Viktor that one of the harder things I have to do is network on LinkedIn. It is our most important recruitment channel, but I did not have the time to turn every idea into a polished post. We built a social media optimization workflow: I share the concept or the talking points, and Viktor crafts them into thoughtful, high-performing posts complete with hashtags and language that sounds like me. Viktor can do that because of every previous interaction we have had. It has learned my voice over time. I approve or edit, Viktor posts. That workflow is still running today.

By early March, CollabNET had grown from an org chart into a full internal workbench: ticketing, volunteer pipeline tracking, self-paced orientation modules, and content management. All on one platform, at cnet.collabed.org.

The real shift happened when Viktor started remembering. Every workflow we built, every preference I corrected, every process we refined got stored in persistent memory. Viktor now holds 58 skill files about how CollabED operates. When I ask for something new, Viktor already knows our department structure, our brand voice, our director list, and our technical setup.

One example: we built a community content sync pipeline that publishes approved posts from CollabNET to our public site at collabed.org. It runs three times daily and has published 112 posts since launch. Every new channel captain who submits content through CollabNET automatically feeds the public site. That one automation replaced a process that previously required me to copy, format, and post each piece of content by hand.

On March 21 at 1 AM, I posted a 47-item checklist to replace Group.app. We knocked out 8 items that first night. By April 15, the DNS was flipped and Group.app was retired.

On April 19, I asked Viktor to build ElevatED, our self-paced course platform. The first version was live by the end of that evening. Two courses were running within a week.

On April 21, I got an email that our Apple Developer account was approved. I messaged Viktor: "What the hell do I do. I have no idea where to even start." I do not own a Mac. Viktor walked me through Bundle ID registration, App Store Connect, found a no-Mac workaround using Codemagic, generated the build, and submitted it. The app was approved the same day. Without Viktor, that would have remained a someday idea.

Kaley used Viktor to design the Mindful Reset app. She also noted the rough edges: a context-switching bug that double-posted a LinkedIn poll, and a platform connection where Viktor reported something fixed before it actually was.

10

Live web platforms (custom subdomains)

2

Mobile apps (iOS live, Android sub.)

27

Daily automations

12

Active integrations

The process has not been perfect. There have been bugs and growing pains. But CollabED now operates on a platform designed intentionally for our needs, rather than one we had to work around.

10 live web platforms on custom subdomains, plus an iOS app in the App Store and an Android app submitted to Google Play — built in 75 days

27 scheduled automations: volunteer birthday reminders, board document signature tracking, grant opportunity monitoring, community post syncing, and more

12 active integrations: Gmail (x2), Google Drive, Google Calendar, Google Contacts, Constant Contact, LinkedIn, Hootsuite, Cloudflare, PDFFiller, Printify, Tawk.to, and Slack

7 days of fully autonomous operation while I was on my first family vacation in a year. Daily status reports, LinkedIn posts, volunteer pipeline management, and domain monitoring all continued without me. Zero issues

Every morning at 10 AM, a status report lands in my Slack DM: domain health across our sites, member count, Constant Contact contacts, synced posts. Viktor has sent that report 39 days in a row without missing one. I did not ask for it. Viktor built the routine after observing how I work.

What surprised me most is what I use Viktor for that I never expected. I did not plan to build mobile apps. I did not plan to replace our community platform. I did not plan to automate board governance. Each of those started as a single conversation and grew because Viktor remembered the context from every conversation before it.

If Viktor were turned off tomorrow, the first thing my team would notice is that the platforms stop updating. Then the automations go silent. Then the integrations between our systems disconnect. Viktor is not one feature we added. It is the infrastructure underneath everything we have built.

I have built an entire web network with Viktor. Slack is where Viktor lives for me, but what we have built together goes well past Slack. For someone outside the tech space, getting something like this off the ground can feel overwhelming. Viktor made it manageable. And then it made it real.