LATITUDE 40
  • Home
  • About Us
    • Who We Are
    • How We Work
    • Our Quality Standards
    • How We Forecast ROI
  • Solutions
    • Custom Software
    • Explore Solutions
  • Successes
    • Case Studies
    • Testimonials
  • Insights
    • Blog
    • ROI Guides
  • Contact

Latitude 40 blog

When Off-the-Shelf Is Absolutely the Wrong Choice (Even If It Looks Cheaper Today)

1/22/2026

0 Comments

 
Off‑the‑shelf (OTS) software carries a powerful promise: quick setup, predictable pricing, and a polished interface that seems to fit your workflows perfectly (at least during the demo).

And while OTS often is cheaper upfront, that’s not universally true. Some specialized OTS platforms cost more than building a modest custom solution. Others charge per user, per location, per integration, per module, or “per something you never thought to ask about.”

So, the real question isn’t: “Is off‑the‑shelf cheaper right now?”
​

It’s: “Does off‑the‑shelf support the business I am today and the business I want to become? ”

Because that second question is where companies either protect their agility… or quietly lose it.
​
Let’s explore the situations where off-the-shelf is absolutely the wrong choice, even when it seems practical at first glance.

​1. When Your Workflows Are Unique (or Should Be)

Every business has two types of workflows:

1. Commodity workflows

These are standardized across industries.

Example: Accounting firms follow the same accounting rules. A standardized accounting platform makes perfect sense because the workflow itself is standardized and legally constrained.

2. Differentiating workflows

These are the processes that make your company yours. How you quote, dispatch, schedule, route, fulfill, quality-check, inspect, coordinate, ship, or serve customers.

OTS software often forces you into workflow patterns that were designed for the “average” customer.

But here’s the nuance most businesses miss: Even if your process isn’t unique today, it could become a competitive advantage tomorrow if you’re able to improve it.

OTS can block that path. Custom software unlocks it.

If your current processes feel generic or inefficient, locking into a rigid OTS tool freezes those weaknesses in place.
​
If you want to gradually refine how you operate, and build differentiation over time, you need flexibility that OTS can’t give you.

​2. When the Tool Dictates Your Process

A common red flag during demos: “Don’t worry. You can adjust your workflow to match how our platform works.”

That sentence sounds harmless, but its implications are expensive. It often means:
  • The vendor’s data model is rigid
  • Their workflow engine is limited
  • Their assumptions about your industry don’t match your reality

Every “simple adjustment” your team makes is a small tax on efficiency. And those taxes compound for years.

If your competitive edge comes from how you operate, OTS can unknowingly dilute that edge.

​3. When Integration Depth Actually Matters

Most OTS tools advertise integrations, but those claims fall into three categories:
​ 
  1. Marketing integrations: they exist, but only in the broadest sense
  2. Shallow integrations: they sync a few fields, not real business logic
  3. Rigid integrations: they only support the vendor’s workflow, not yours

Even one missing field or unsupported workflow can derail an entire automation.

The complexity isn’t the API. It’s the nuances of your data and business rules. Those never align perfectly with an OTS platform.

When integration is important (and it almost always is), OTS solutions often turn into patchwork systems with spreadsheets, Zapier chains, and manual cleanup behind the scenes.
​
That’s inefficient and fragile.

​4. When You Expect Your Business to Evolve

Markets shift. Teams adapt. Processes get refined. Regulations change. Your customers expect more tomorrow than they do today.

But OTS vendors evolve based on their priorities, not yours.

Even if a vendor’s current roadmap seems aligned with your needs:
  • Roadmaps change
  • Priorities shift
  • Companies get acquired
  • Features get sunset
  • Pricing models get restructured

You have zero control over those timelines.
​
If you need the ability to evolve rapidly, OTS systems can become bottlenecks just when you need flexibility most.

​5. When Compliance Changes Aren’t Frequent or Costly

There is a category of OTS platforms that actually make sense long-term: Product-as-a-service systems

These tools don’t just store data. They stay up to date on your behalf.

Examples:
  • HR platforms that automatically track employment law changes in all 50 states
  • Tax systems that update formulas as regulations shift
  • Compliance platforms that push out mandated updates

In these cases, buying is smarter than building.

You’re paying for far more than software. You’re paying for a service that delivers continuous compliance updates from experts you don’t have to hire.

These are the rare OTS tools that may become more valuable over time, not less.

​6. When Workarounds Become Standard Operating Procedure

If your team uses:
  • parallel spreadsheets
  • duplicate data entry
  • shared inboxes for workflows
  • shadow systems
  • scripts to cleanup exports
  • manual adjustments before imports

…it’s a sign the OTS tool isn’t aligned with your real operations.

Workarounds are silent costs. They drain morale. They slow down training. They guarantee mistakes. And they accumulate into a workflow you never intended.
​
Once your organization builds habits around these workarounds, unwinding them becomes even more expensive than building the right solution yourself.

​When Off-the-Shelf Is the Right Choice

OTS is often the best fit when:
  • The process is legally, operationally, or mathematically standardized
  • The software includes built‑in expertise that would be expensive to maintain internally
  • You don’t need deep integrations or custom logic (although you will likely realize later that you DO need these integrations)
  • You’re not differentiating based on that workflow

The key is to validate real alignment, not demo alignment.

Don’t trust the sales pitch.

Don’t trust the checklist.

And don’t assume the roadmap will remain stable.

​OTS is right when the workflow itself is a commodity and wrong when the workflow is a strategic asset.

​Final Thought

The danger with OTS software isn’t the cost. It’s the rigidity.

Off-the-shelf tools look economical on Day One.

But when they restrict how your business evolves (or worse, lock your inefficiencies in place) they become one of the most expensive decisions you can make.

At Latitude 40, our advice is simple:
  • Buy OTS for standardized processes.
  • Build when your workflow is your competitive advantage
  • — or when you want it to become one.

Your business deserves software that fits the way you actually work, and the way you intend to work in the future.

​About Latitude 40

Latitude 40 is a U.S. based software development company focused on helping businesses stay lean, responsive, and ahead of the curve. Our experienced on-shore professionals work alongside your team to deliver tailored solutions that solve real business challenges.
​
We emphasize reducing risk through thoughtful, incremental improvement and designing systems that deliver measurable ROI. Every engagement is built to strengthen your operations today while giving you the flexibility to adapt tomorrow. Technology should be a growth engine, not a roadblock.

​About the Author

​Andrew Anderson is the President of Latitude 40 and a seasoned technology leader with over two decades of experience in software development, architecture, and process improvement. He specializes in helping organizations achieve operational excellence through practical, low-risk strategies that deliver measurable results. Andrew’s approach combines technical expertise with a deep commitment to agility, guiding teams toward smarter solutions and sustainable growth.
0 Comments

Forecasting Software ROI: Part 3 - The Essentials Every Leader Should Know

12/10/2025

0 Comments

 
Graphs and charts showing ROI for a software initiative

​The Foundation for Smarter Software Investments

This article is part of our Forecasting Software ROI series. If you need the full framework, start with Part 1. If you’re comparing custom vs. off-the-shelf, check out Part 2.

When it comes to software investments, most leaders want one thing: confidence that the decision will pay off. But ROI isn’t hiding in license fees or implementation costs. It’s in the value you can’t see at first glance. Faster processes, fewer errors, happier customers, and resilience when things change often drive the biggest gains.

Part 3 of our Forecasting Software ROI series distills the essentials every leader should know about building credible ROI forecasts. This isn’t a deep technical guide (that’s what Part 1 covers) but it will help you understand the principles behind a risk-aware, defensible ROI model.

​What You’ll Learn in Part 3

This article is designed for decision-makers who need clarity without getting lost in the details. You’ll learn:
  • Why quick cost comparisons fail and what makes a forecast credible
  • The four pillars of ROI forecasting:
    • Start with your current state: Map workflows and baseline metrics
    • Model multiple drivers: Go beyond labor savings to include quality improvements, experience, and risk
    • Use ranges and confidence factors: Show variability and transparency
    • Compare multi-year benefits to total cost: Reflect the full lifespan of value
  • How strategic factors like adaptability, control, and ownership amplify ROI over time

​If you want the full framework, Part 1 is your deep dive while Part 2 illustrates how going custom changes the ROI equation.

-> Download Part 3: Essentials Every Leader Should Know (PDF)

​Explore the Complete Guide Series

Part 1 – A Practical Framework
Part 2 – Custom vs. Off-the-Shelf
Part 3 – Essentials Every Leader Should Know (You’re here)

There’s more to come!

​About Latitude 40

Latitude 40 is a U.S.-based software development partner focused on helping businesses stay lean, responsive, and ahead of the curve. Our experienced on-shore professionals work alongside your team to deliver tailored solutions that solve real business challenges.
​
We emphasize reducing risk through thoughtful, incremental improvement and designing systems that deliver measurable ROI. Every engagement is built to strengthen your operations today while giving you the flexibility to adapt tomorrow. Technology should be a growth engine, not a roadblock.

​About the Author

​Andrew Anderson is the President of Latitude 40 and a seasoned technology leader with over two decades of experience in software development, architecture, and process improvement. He specializes in helping organizations achieve operational excellence through practical, low-risk strategies that deliver measurable results. Andrew’s approach combines technical expertise with a deep commitment to agility, guiding teams toward smarter solutions and sustainable growth.
View my profile on LinkedIn
0 Comments

Forecasting Software ROI: Part 2 - Custom vs. Off-the-Shelf

12/2/2025

0 Comments

 
Charts and graphs showing ROI for a software project

​Custom vs. Off-the-Shelf: The ROI Question

This post is part of our ongoing Forecasting Software ROI series, created to help leaders make smarter software investment decisions. If you haven’t read Part 1 yet, start with A Practical Framework for ROI Forecasting.

If you’re here, you already know ROI forecasting matters. But here’s the real question: how does your choice between custom and off-the-shelf software change the ROI equation?

This isn’t just about features or price tags. It’s about how well your system fits your business today, and how easily it adapts tomorrow. In Part 2, we go beyond theory and show you what happens when better fit, adaptability, and control become part of the ROI picture.

What You’ll Learn in Part 2

  • How a better fit pays off with fewer errors and faster processes
  • Why adaptability is a competitive edge when regulations or markets shift
  • How control turns risk into resilience by eliminating vendor-driven surprises
  • Why ownership matters for long-term value and stability
Through real-world scenarios and risk-adjusted numbers, you’ll see how these factors change the ROI equation and why custom software often delivers value far beyond upfront cost.
​
​-> Download Part 2: Custom vs. Off-the-Shelf ROI Lenses (PDF)

​Explore the Complete Guide Series

Part 1: A Practical Framework
Part 2: Custom vs. Off-the-Shelf (You’re here)
Part 3: Essentials Every Leader Should Know

There’s more to come!

​About Latitude 40

Latitude 40 is a U.S.-based software development partner focused on helping businesses stay lean, responsive, and ahead of the curve. Our experienced on-shore professionals work alongside your team to deliver tailored solutions that solve real business challenges.
​
We emphasize reducing risk through thoughtful, incremental improvement and designing systems that deliver measurable ROI. Every engagement is built to strengthen your operations today while giving you the flexibility to adapt tomorrow. Technology should be a growth engine, not a roadblock.

​About the Author

​Andrew Anderson is the President of Latitude 40 and a seasoned technology leader with over two decades of experience in software development, architecture, and process improvement. He specializes in helping organizations achieve operational excellence through practical, low-risk strategies that deliver measurable results. Andrew’s approach combines technical expertise with a deep commitment to agility, guiding teams toward smarter solutions and sustainable growth. 
View my profile on LinkedIn
0 Comments

Forecasting Software ROI: Part 1 - A Practical Framework

11/20/2025

0 Comments

 
Charts and graphs showing the forecasted ROI for an upcoming software project

Launching Our Forecasting Software ROI Series

How do you know software will pay off? Most leaders wrestle with this question, and the answer isn’t as simple as comparing license fees or implementation costs. ROI forecasting is about more than cost. It’s about understanding where value really comes from.

We’re creating a new series called Forecasting Software ROI to help companies make smarter software investment decisions. Each part will tackle a different angle, from practical steps to strategic considerations, so you can build forecasts that leadership can trust.

Part 1: A Practical Framework for ROI Forecasting

This first installment lays the foundation, and it’s the most detailed part of the series. Why? Because building a credible ROI forecast isn’t a quick exercise. It requires mapping your current state, modeling multiple drivers, applying ranges and confidence factors, and comparing multi-year benefits to total cost.

In Part 1, we break down these steps into a structured approach you can follow. It’s not light reading, but it’s designed to give you clarity and confidence when the stakes are high.
​
-> Read the full guide here: Part 1: A Practical Framework for ROI Forecasting (PDF)

​What’s Coming Next

Read Part 2: Custom vs. Off-the-Shelf and learn how adaptability, control, and ownership are  strategic advantages that amplify ROI over time.
​
And we’re just getting started. Future parts will cover executive essentials, common pitfalls, and advanced techniques for modeling ROI.

​Explore the Complete Guide Series

Part 1: A Practical Framework (You’re here)
Part 2: Custom vs. Off-the-Shelf
Part 3: Essentials Every Leader Should Know
​
There’s more to come!

​About Latitude 40

Latitude 40 is a U.S.-based software development partner focused on helping businesses stay lean, responsive, and ahead of the curve. Our experienced on-shore professionals work alongside your team to deliver tailored solutions that solve real business challenges.
​
We emphasize reducing risk through thoughtful, incremental improvement and designing systems that deliver measurable ROI. Every engagement is built to strengthen your operations today while giving you the flexibility to adapt tomorrow. Technology should be a growth engine, not a roadblock.

​About the Author

​Andrew Anderson is the President of Latitude 40 and a seasoned technology leader with over two decades of experience in software development, architecture, and process improvement. He specializes in helping organizations achieve operational excellence through practical, low-risk strategies that deliver measurable results. Andrew’s approach combines technical expertise with a deep commitment to agility, guiding teams toward smarter solutions and sustainable growth.
View my profile on LinkedIn
0 Comments

From Chaos to Control: Moving from Spreadsheets to FileMaker

11/7/2025

0 Comments

 
A man frustrated with too many spreadsheets

​Introduction

Startups thrive on agility and cost-efficiency. With limited cash flow, spreadsheets often become the go-to tool for managing everything: sales, inventory, finances, and more. They’re familiar, flexible, and free. But as your business scales, spreadsheets start showing cracks that can cost you time, money, and credibility.

​Your Business Has Evolved—Has Your Data?

​Spreadsheets are fantastic for getting started. They’re simple, flexible, and cost-effective. But as your business grows, the demands on your data grow too. What worked for a handful of customers or a few transactions can quickly become a bottleneck when you’re scaling. 
Here are the signs your data hasn’t kept up with your business: 
  • Manual Processes Everywhere: Entering the same customer details in multiple sheets wastes time and invites errors. 
  • Fragile Formulas: One accidental deletion can throw off entire reports. 
  • Version Chaos: Multiple copies mean no single source of truth. 
  • Security Gaps: Anyone can overwrite or delete critical information. 
  • Complexity Overload: Adding more tabs and links makes spreadsheets harder to manage and easier to break. 
If this sounds familiar, it’s time to level up. Your business deserves a system that grows with you, not one that holds you back.

​Why FileMaker is the Next Logical Step

When your startup outgrows spreadsheets, you need a solution that’s just as flexible but far more reliable. FileMaker offers:
  • Effortless Migration: Import your existing spreadsheet data in minutes.
  • Data Security: Protect your information and formulas from accidental changes.
  • Customizable Layouts: Easily modify screens, add new fields, and create reports.
  • Built-In Calculations: Keep your logic consistent and safe across the system.
  • Relational Design Eliminates Duplicate Entry: Enter data once and use it everywhere. For example, a customer record can link to invoices, orders, and reports without retyping the same details.​
  • Scalable Design: Start small and expand as your business 

​The Bottom Line

​Spreadsheets are great for starting out, but they’re not built for scale. FileMaker bridges the gap from spreadsheets to a fully customized solution, giving you the flexibility you love with the security and structure you need.

​About Latitude 40

Latitude 40 integrates experienced on-shore software development professionals into your organization, forming collaborative teams with or without your existing developers. Together, we identify needs, create tailored software solutions, and instill best practices that drive continuous improvement and ensure agility.

Ready to move beyond spreadsheets? Start your FileMaker journey today.

About the Author

​Dan DeLeeuw is the Chief Operating Officer at Latitude 40 Consulting and a Certified FileMaker Developer. He consistently maintains the latest FileMaker certifications, reflecting his commitment to staying at the forefront of the platform. Dan is a strong advocate for clean, maintainable, and well-documented code, believing that clarity is key to scalable and sustainable development.
0 Comments

Reducing Your Risk of Change Through Thoughtful, Incremental Improvement

10/29/2025

0 Comments

 
New stairs take you gradually up to the top of the mountain with clear, blue skies above.
Change is risky. But stagnation is riskier.

At Latitude 40, we work with organizations that know they need to evolve, but want to do so without jeopardizing what's already working. Whether you're refining internal processes, upgrading systems, or rethinking how teams operate, the safest and smartest way to move forward is usually through thoughtful, incremental improvement.

The Hidden Risk of Standing Still

It's tempting to delay change in the name of stability. But over time, that stability becomes fragility. Processes grow outdated. Systems become bottlenecks. Teams adapt in ways that mask deeper issues. The longer you wait, the harder it becomes to respond when change is finally unavoidable.

In today's environment, stagnation isn't neutral, it's a liability. The cost of doing nothing often exceeds the cost of doing something imperfectly.

So how do you move forward without introducing unnecessary risk?

Why Big Change Often Backfires

Many organizations respond to mounting pressure with sweeping, all-at-once transformation. New systems, new processes, new roles. Everything changes at once. But this “big bang” approach often creates more problems than it solves.

Operations get disrupted. Teams feel overwhelmed. And the assumptions baked into the plan (however well-intentioned) don’t always hold up in practice.
​
Even when large-scale change is necessary, trying to solve everything up front assumes you already know the right answers. But in reality, the best solutions often emerge through deeper thought, experimentation, and iteration.

The Power of Moving Deliberately

Incremental improvement isn’t about moving slowly. It’s about moving intentionally. It allows you to:
  • Refine your approach as you go: Each step is a chance to learn, adjust, and improve the next.
  • Think deeply and experiment: Some problems require exploration. A phased approach gives you room to test ideas before committing.
  • Avoid analysis paralysis: You don’t need a perfect plan to start. You just need a smart first step.
  • Deliver impact early: Small wins deliver value early without waiting for a full overhaul. They also build momentum and confidence.
This mindset helps reduce risk, preserve continuity, and build trust across the organization.

Custom Software: A Natural Fit for Continuous Improvement

One of the most powerful enablers of incremental change is custom software.

Imagine a continuous improvement team moving through your organization, tackling whatever is most important at the time. They identify bottlenecks, streamline workflows, and improve outcomes. But when they encounter rigid, off-the-shelf systems, progress stalls. The software becomes a bottleneck unable to adapt to the evolving needs of the business. Even if the software was the perfect fit originally, it may no longer be.

Custom software changes that dynamic. It’s built to evolve. It allows your team to respond to insights quickly, implement changes without waiting on a vendor roadmap, and align technology with strategy in real time.
​
In short, custom software doesn’t just support continuous improvement. It unlocks it.

Our Approach at Latitude 40

We help clients identify the smallest meaningful change that moves them forward. Then we work alongside their teams to deliver it collaboratively. Whether that means building a custom application, creating integrations, refining a workflow, or enabling better decision-making, we guide change with purpose.
​
We don’t push transformation for transformation’s sake. We build solutions that support agility, experimentation, and long-term growth without introducing unnecessary risk.

Final Thought

Change doesn’t have to be scary. When it’s thoughtful and incremental, it becomes a source of strength. And when paired with flexible, custom-built tools, it becomes a competitive advantage.

Build momentum, not disruption. Let’s get started.

About Latitude 40

​Latitude 40 integrates experienced on-shore software development professionals into your organization, forming collaborative teams with or without your existing developers. Together, we identify needs, create tailored software solutions, and instill best practices that drive continuous improvement and ensure agility.

About the Author

Andrew Anderson is the President of Latitude 40 and a seasoned technology leader with over two decades of experience in software development, architecture, and process improvement. He specializes in helping organizations achieve operational excellence through practical, low-risk strategies that deliver measurable results. Andrew’s approach combines technical expertise with a deep commitment to agility, guiding teams toward smarter solutions and sustainable growth.
View my profile on LinkedIn
0 Comments

AI-Washing: The New Greenwashing in Software

10/14/2025

0 Comments

 
Custom software is utilizing AI tooling for optimum results.

​The AI Hype Is Real - But So Is the Confusion

Artificial intelligence is everywhere… or at least, that's what the marketing says. From "AI-powered" dashboards to "intelligent" assistants, it seems like every software product has suddenly become sentient.

But when you dig beneath the surface, many of these so-called AI features are just automation in disguise. Automation is powerful and impactful, so that's not a criticism. But calling everything "AI" muddies the waters.

We call this AI-washing, and it's becoming the new greenwashing, the marketing trend starting in the 2000s where companies started exaggerating their environmental friendliness to appeal to eco-conscious consumers. Products were labeled "green" or "eco-friendly" without meaningful changes to how they were made or used.

Why AI-Washing Hurts

AI-washing happens when companies label something as "AI" to make it sound more advanced than it really is. Even when unintentional resulting from misunderstanding or overzealous marketing, the impact is real:
  • Clients chase complexity they don't need: Companies may worry that their current tooling isn't "AI-driven" and fear they're falling behind. This FOMO can lead to rushed decisions, vendor churn, and replacing perfectly good systems with more expensive, less maintainable ones.
  • Budgets balloon trying to implement tech that doesn't fit: AI often requires data pipelines, model training, monitoring, and specialized infrastructure. If the problem doesn't warrant that investment, it's wasted effort.
  • Trust erodes when "AI" doesn't deliver: When expectations are set by marketing rather than reality, disappointment is inevitable; and it reflects poorly on vendors and internal teams alike.
Sometimes all you need is good old-fashioned automation. A client recently came to us asking for an "AI-powered scheduling assistant." After a few conversations, it became clear they didn't need AI at all. They needed a rules-based system that could assign jobs based on technician availability and skillset. No machine learning required.

Automation and AI Overlap

Here's where the confusion often starts: automation and AI aren't opposites, and they're not interchangeable. They exist on a spectrum and often work together.
  • Automation handles predictable, repeatable tasks. It's built on logic, rules, and workflows.
  • AI handles uncertainty, pattern recognition, and probabilistic decision-making.
Sometimes, automation uses AI as an ingredient. For example, a document upload process might use an AI model to extract text from images or classify content, but the rest of the workflow is pure automation.

That doesn't make the whole system "AI-powered." But it also doesn't mean AI isn't involved in a very helpful way.

Not All AI Is Complex - And That's Okay

You don’t need a self-learning model running 24/7 to benefit from AI. Sometimes, a simple occasional use of AI (like using it to summarize a paragraph) is all you need.

That's still AI. It's just lightweight and task-specific.

The key is understanding what role AI plays in your system, and whether it's solving a problem that actually requires it.

When Complex AI Is Worth It

While some AI use cases are lightweight and task-specific, others truly benefit from deeper investment and deliver transformative results when done right.

For example:
  • Predictive maintenance systems in manufacturing use historical sensor data to forecast equipment failures before they happen. These models require training, tuning, and ongoing monitoring, but they can save millions in downtime.
  • Fraud detection in financial services often relies on anomaly detection algorithms that evolve as new fraud patterns emerge. These systems need constant refinement and access to large, diverse datasets.
  • Natural language processing for customer support can go far beyond simple chatbots. With the right training, AI can understand intent, sentiment, and context which can reduce support costs while improving the customer experience.
These aren't plug-and-play solutions. They may require:
  • Clean, well-structured data
  • A clear understanding of the problem space
  • Collaboration between domain experts and data scientists
  • Ongoing evaluation and iteration
But when the problem is complex, dynamic, and data-rich, AI may be essential to staying relevant.

How We Help Clients Cut Through the Noise

At Latitude 40, we don't lead with buzzwords. We lead with questions:
  • What problem are you trying to solve?
  • What decisions need to be made?
  • What data do you have?
  • What would success look like?
Sometimes the answer is AI. Sometimes it's automation. Sometimes it's just a better process. Our job is to help you figure that out and build something elegant, maintainable, and effective.

​AI is a tool. Automation is a tool. So is a thoughtfully designed workflow. The key is knowing when to use which and having a partner who can help you decide.

Final Thought

If you're evaluating a product or planning a new system, don't start with "we need AI." Start with the problem. Then find the simplest, smartest way to solve it.

That's how we work. And that's how we help our clients move faster, with or without AI.

About Latitude 40

Latitude 40 helps businesses achieve operational excellence and long-term business agility through tailored software solutions and expert guidance. By embedding into client teams, Latitude 40 delivers elegant, maintainable software while teaching Agile practices that foster sustainable growth. Latitude 40 builds with clarity, purpose, and a deep respect for the people who maintain and evolve code.

Have questions about incorporating AI into your custom applications? Let’s talk.

About the Author

Andrew Anderson is President of Latitude 40 Consulting and a seasoned software architect with over two decades of experience in developing Agile solutions. He's worked globally as a developer, analyst, and instructor, and is passionate about writing maintainable code and helping teams grow through clean architecture and the Agile mindset. Andrew shares insights from the field to help developers and leaders build better software, and better teams.
View my profile on LinkedIn
0 Comments

From Keywords to Meaning: How AI Powers Semantic Searches

10/2/2025

0 Comments

 

​Understanding Semantic Searches

Traditional keyword search is like looking for a needle in a haystack—if you don’t use the exact word, you might miss the match. Semantic search changes that by focusing on meaning rather than literal words.

Instead of searching through a database of book reviews for "Romance" or "Suspense", imagine typing:
  • "Get the heart racing" and finding reviews like:
    • "I couldn't put it down."
    • "It kept me up all night."
Or searching for:
  • "Excites the heart" and discovering:
    • "A passionate love story that lingers long after the last page."
      ​
Semantic search understands the search intent and emotion behind your query, not just the vocabulary. To make semantic searches possible, AI uses a concept called vector embeddings

​What are Vector Embeddings?

AI models convert text into vector embeddings—arrays of numbers that represent meaning in a multi-dimensional space.
  • Each word or phrase becomes a token.
  • These tokens are plotted in a space with hundreds or thousands of dimensions.
  • Words with similar meanings are placed closer together.
    ​
Think of it like a galaxy of ideas, where “thrilling” and “exciting” orbit near each other, while “boring” floats far away.

​A Cosine Similarity: Measuring Meaning

Once text is embedded into vectors, we need a way to compare them. That’s where cosine similarity comes in.
  • It measures the angle between two vectors.
  • A score near 1 means the vectors (and thus the meanings) are very similar.
    ​
Cosine similarity is the engine behind semantic matching.

Claris ​FileMaker’s New Semantic Search Features

Claris FileMaker Developers now have AI script steps that make semantic search easy to implement.
  • You can embed text, store vectors, and compare them—all within FileMaker and an AI Language Model from a company such as Cohere.
  • This enables smarter search experiences, like:
    • Matching user queries to emotionally resonant reviews.
    • Finding relevant content even when keywords don’t match for better workflow optimization.

​About Latitude 40

Latitude 40 integrates experienced on-shore software development professionals into your organization, forming collaborative teams with or without your existing developers. Together, we identify needs, create tailored software solutions, and instill best practices that drive continuous improvement and ensure agility.

Contact Latitude 40 to learn how we can help implement AI into your Claris projects.​

About the Author

​Dan DeLeeuw is the Chief Operating Officer at Latitude 40 Consulting and a Certified FileMaker Developer. He consistently maintains the latest FileMaker certifications, reflecting his commitment to staying at the forefront of the platform. Dan is a strong advocate for clean, maintainable, and well-documented code, believing that clarity is key to scalable and sustainable development.
0 Comments

Clean Code: Mindset Over Dogma

9/18/2025

0 Comments

 
Developer is sitting at her desk with multiple monitors thinking about the design of a software system she's helping write.
Lately, I've seen a wave of criticism and developer backlash against clean code. They argue it's too rigid, too idealistic, and often counterproductive. They point to over-engineered systems filled with tiny methods, excessive abstraction, and unnecessary complexity, all in the name of "clean code."

But this criticism often confuses the mindset with its misapplication. Clean code isn't a checklist or a burden. It's a way of thinking about how your code will be understood, maintained, and extended by others.

The Mindset vs. the Mechanics

Clean code is not a set of rules to follow blindly. It's a mindset with a commitment to clarity, maintainability, and empathy for the next developer. The techniques commonly associated with clean code (like meaningful naming, small functions, and separation of concerns) are tools that support this mindset. They're not mandates.

When developers apply these techniques without understanding the why, they risk creating code that's technically "clean" but practically unreadable. The mindset encourages thoughtful application, not dogmatic adherence.

Why It Matters in the Enterprise

In enterprise environments, code lives longer, changes hands more often, and supports critical systems. Maintainability is a necessity. Clean code helps teams avoid technical debt, reduce onboarding time, and improve collaboration.

Even if you don't apply every principle, understanding the mindset helps you make better decisions. It's not about perfection. It's about writing code that others can work with confidently.

Clean Code Is Empathy in Action

At its core, clean code is about empathy. It's about writing software that respects the time and effort of others. It's about leaving behind code that's easy to read, change, and build upon.

This mindset fosters trust, reduces bugs, and makes teams more resilient. It's not just about how the code looks, it's about how it feels to work with.

Conclusion: Don't Reject the Mindset

Let's be clear: you absolutely shouldn't reject the clean code mindset. If you choose to skip the education and experience that comes from practicing clean code, you're not just avoiding a style. You’re limiting your growth as a developer.

Clean code principles teach you how to think about architecture, readability, and long-term maintainability. These are the skills that separate good developers from great ones. They're far more important than knowing the latest language features or syntax tricks.

Languages change. Frameworks evolve. But the ability to write code that others can understand, maintain, and extend is timeless.

About Latitude 40

Latitude 40 helps businesses achieve operational excellence and long-term business agility through tailored software solutions and expert guidance. By embedding into client teams, Latitude 40 delivers elegant, maintainable software while teaching Agile practices that foster sustainable growth. Latitude 40 builds with clarity, purpose, and a deep respect for the people who maintain and evolve code.

Need help cleaning up a messy codebase or modernizing your systems? Let’s talk.

About the Author

Andrew Anderson is President of Latitude 40 Consulting and a seasoned software architect with over two decades of experience in Agile delivery. He's worked globally as a developer, analyst, and instructor, and is passionate about writing maintainable code and helping teams grow through clean architecture and practical Agile practices. Andrew shares insights from the field to help developers and leaders build better software, and better teams.
View my profile on LinkedIn
0 Comments

Don't Trust the Docs: Why API Documentation is Often Just Marketing

9/12/2025

0 Comments

 
A vibrant cityscape at dusk featuring large illuminated digital billboards advertising Coca-Cola Zero, Samsung, TDK, Hyundai, and Vogue. A red double-decker bus with an ad for
When evaluating third-party APIs, the documentation is usually your first stop. It's polished, promising, and full of potential. But here's the uncomfortable truth: API documentation is often more marketing than engineering. It's designed to sell you on the idea that integration will be smooth, powerful, and fast. What it doesn't show are the bugs, the limitations, and the painful workarounds you'll only discover once you're deep into development.

The Hidden Cost of Optimism

It's not just technical decisions that hinge on documentation; it's budgeting, timelines, and even product selection. Teams read the docs, see the capabilities, and assume they're real. They plan around them. They fund projects based on them. And when the reality doesn't match the promise, the fallout can be significant.

In one project we worked on recently, our client chose to use a major enterprise product largely because of its advertised integration capabilities. The documentation made it look like a perfect fit. But once we started building, we found that many documented APIs simply didn't work. Some returned internal server errors when used exactly as described. Others had bizarre side effects like updating one field and unintentionally clearing out others, forcing us to implement multi-step workarounds just to preserve data integrity where we could.

The client had already committed budget and resources based on the assumption that integration would be straightforward. Had they known the true state of the API, they might have chosen a different product entirely.

We've actually seen similar examples time and time again (which is why I decided to write about this).

Why Documentation Misleads

Most API documentation is written to attract business and developers, not warn them. It highlights features, not flaws. It shows clean examples, not edge cases. It never mentions:
​
  • Inconsistent or unstable endpoints
  • Poor versioning or breaking changes
  • Internal quality concerns within the product itself
  • Lack of support or slow bug resolution

Even SDKs and sample code are often designed to show the "happy path," not the real-world complexity of integrating with a system that is under-documented or poorly maintained.

How to Protect Yourself

Before you commit to an API, build a prototype. Don't just read the docs. Test the endpoints. Try the edge cases. See how the system behaves under real conditions. And look beyond the vendor's website:

  • Check GitHub issues and changelogs
  • Search developer forums and Reddit threads
  • Evaluate SDK quality and update frequency
  • Ask about support responsiveness and roadmap transparency

This may take some time and funding, but it is worth it!

Conclusion

API documentation is a sales pitch. It's useful, but it's not the whole story. Treat it like marketing material. It's something to be verified, not trusted blindly. Because once you've committed to a product based on fictional capabilities, the cost of backing out can be steep.

About Latitude 40

Latitude 40 integrates experienced on-shore software development professionals into your organization, forming collaborative teams with or without your existing developers. Together, we identify needs, create tailored software solutions, and instill best practices that drive continuous improvement and ensure agility.

Need help cleaning up a messy codebase or modernizing your system? Let's talk.

About the Author

​Andrew Anderson is the President of Latitude 40 and a lifelong advocate for clean, maintainable code. With over two decades of experience as a developer, analyst, and Agile coach, he’s worked globally to help teams build better software and embrace sustainable delivery practices.
View my profile on LinkedIn
0 Comments
<<Previous

    Categories

    All
    Agile
    Claris
    Clean Code
    Custom Vs. Off The Shelf
    Forecasting ROI
    On-shoring
    Technical
    Tech Strategy

    RSS Feed

Copyright © 2025 Latitude 40 Consulting, Inc.  All rights reserved.
Latitude 40® is a trademark of Latitude 40 Consulting, Inc. All other trademarks are the property of their respective owners.
Picture
11001 W. 120th Ave. ​Suite 400
Broomfield, CO 80021
303-544-2191
CONTACT US
privacy policy
terms of service
blog index
customer login
  • Home
  • About Us
    • Who We Are
    • How We Work
    • Our Quality Standards
    • How We Forecast ROI
  • Solutions
    • Custom Software
    • Explore Solutions
  • Successes
    • Case Studies
    • Testimonials
  • Insights
    • Blog
    • ROI Guides
  • Contact