The seven-year evolution from customer request to elegant two-rule solution at Tallyfy. Why checkboxes beat flowcharts for handling complex approval rejections and re-work scenarios in workflow automation.
Nobody reads their 47th task reminder. The Tallyfy engineering team learned this the hard way building 77 email templates across 6 locales. The daily digest became our answer, an activity-stream approach that pulls people in instead of pushing them away. Here is the engineering story behind reminder emails that actually get opened.
Building Tallyfy Sherlock, an if-this-then-that rules engine for workflow automation, from April 2018. The internal debates, the disagreements on scope, and why testing rules before deployment became the defining feature.
Most companies already have SOPs in Word or PDF format. Tallyfy built document-to-workflow parsing from 2017 to present, evolving from flowchart annotation ideas to AI-powered conversion that processes complex documents in 24 seconds or more.
Swimlane diagrams capture three dimensions most workflow tools miss: what needs doing, who does it, and when. A typical employee review takes 143 minutes of work spread across 17 business days and four departments. Tallyfy tracks all three at the template level so handoffs stay visible.
Why Tallyfy built custom SAML 2.0 authentication instead of paying Okta or Auth0. The real cost of enterprise SSO, certificate management, SCIM provisioning for organizations with 5000-plus users, and a private key exposure vulnerability in API responses.
The biggest problem in workflow software was never technical. It was getting team agreement on who does what. This 2017 insight at Tallyfy shaped eight years of product decisions.
Templates and processes live in separate folders at Tallyfy because they represent different modes of work. The blueprint versus instance mental model, influenced by tag-based models like Gmail, took years to communicate effectively.
When your shipping process differs slightly by country, most teams clone their template fifteen times. This creates a maintenance nightmare. At Tallyfy, we designed a better approach: define variations from Standard and visualize the difference between one variation and another.
The Tallyfy permission matrix for watchers turned out simpler than expected. If you can edit an object, you can edit its watchers. That single rule drove most of the design decisions behind three watch ownership types.
Favorites in a business context does not really mean anything. At Tallyfy, we redesigned the entire notification system around what Jakob Nielsen called the 1% rule - 90% of users observe rather than create. The familiar star icon stayed but everything underneath changed to support three notification frequencies and process-level watching.
At Tallyfy, we started building a separate EPIC for webhook subscriptions, letting users subscribe to specific events via API endpoints. Then we realized it overlapped with the watching system. The notification target became just another channel: email or webhook.
How Tallyfy engineered deadline calculations that respect business hours, weekends, and timezones. The 2-hour default disaster, the Friday 4:30pm problem, and why user-level working hours had to wait.
Believe.Digital, a 10-person UK digital marketing agency, used Tallyfy to share specialized knowledge across a growing team. With dozens of blueprints covering SEO onboarding, Google Ads management, and web development, apprentices now work at founder-level quality and the founder can step away without worry.
Bricks and MiniFigs replaced tedious manual franchise coordination with a structured Tallyfy candidate dashboard. Carson, their Franchise Development Coordinator, explains how franchise candidates now see exactly where they are in the 30+ step discovery process, what comes next, and why the system doubles as a natural qualification filter.
As Corestream scaled their project management platform, they used Tallyfy workflow automation to eliminate manual errors and accelerate onboarding. Documented workflows replaced scattered communication and preserved institutional knowledge.
Gaylor Electric grew from $400M to $500M in revenue while adding 100 people per month. VP of IT Joe Meadors explains how bi-weekly Tallyfy calls turned executive policy approvals from ad-hoc email chains into a structured process that everyone at the company knows by name.
n8n, created by Jan Oberhauser, charges per workflow execution not per operation - a 200-node workflow costs the same as a 2-node one. That sounds great until you hit the steep learning curve and self-hosting burden that technical teams need to evaluate first.
Simploy, a Professional Employer Organization, cut weekly client meetings from 90 minutes to 20 minutes using Tallyfy. Their onboarding and workers comp renewal processes eliminated duplicated work and the need to chase people for updates.
West Community Credit Union struggled to manage marketing workflows across multiple campaigns. With 50+ step processes and vendor file transfers, things were falling through the cracks. Tallyfy brought clarity and accountability.
These 21 change management quotes from Peter Drucker, Satya Nadella and W. Edwards Deming address why organizational change fails 60% to 80% of the time and what actually makes it stick.
Continuous improvement sounds nice until you try to do it every day. These 24 quotes from Masaaki Imai, W. Edwards Deming, and other operational leaders reveal what sustained improvement actually takes.
Most delegation advice sounds nice but fails in practice. These 20 quotes from leaders like Peter Drucker and Warren Buffett reveal what real delegation requires.
Generic leadership quotes do not fix broken operations. These 22 operational excellence quotes from W. Edwards Deming, Taiichi Ohno, Masaaki Imai, and five other leaders come from people who ran real operations. Deming showed that 85% of quality problems trace to the system, not the person.
