Introduction
For decades, charging by the hour made perfect sense.
Software was built by hand. Engineers wrote code line by line, integrations were fragile, and quality depended on careful craftsmanship. Architects, engineers, and domain experts made critical decisions every day, translating business intent into reliable systems through sustained human effort. The value of services was tightly coupled to experience, judgment, the right mix of roles, and the time invested. In that world, hours were a reasonable proxy for value.
That expertise mattered deeply then, and it matters even more now. Working exclusively as a pure-play Snowflake partner has made this shift impossible to ignore. Snowflake sits at the intersection of data, AI, and consumption-based economics, which means changes in how value is created show up earlier and more clearly. What we see is not the erosion of expertise, but a fundamental change in how it is applied.
What has changed is not the importance of architects and engineers, but where their value is expressed. We no longer need to spend months writing code by hand to demonstrate skill. AI can generate much of the mechanical execution. Code is still essential, but it is now the mechanism, not the value itself.
Today, the highest leverage comes from steering the solution: understanding what the code is doing, ensuring it reflects business intent, orchestrating and governing AI agents, and taking responsibility for how systems behave in the real world. Expertise has moved upstream, from manual execution to design, oversight, and orchestration.
In the past, value was created by building software over time. Today, value is created by deciding what should be built, how it should behave, and what outcomes it must deliver.
Services are still critical. They are just no longer delivered or priced around hours.
Why Hourly Pricing Worked for So Long
Hourly pricing was not an accident or a failure of imagination. It emerged because it aligned reasonably well with how value was created.
Software development and data engineering were execution-heavy disciplines. Progress depended on sustained human effort across many roles: architects to design systems, engineers to implement them, QA to validate them, and project managers to coordinate everything. Complexity increased linearly with scope, and time was a fair proxy for cost and value.
In that environment, paying for hours meant paying for risk reduction. Customers were buying confidence that skilled professionals were applying their judgment carefully, step by step, to systems that mattered.
This model supported decades of innovation. It rewarded craftsmanship, experience, and depth. It worked because effort and outcome were closely linked.
The Structural Break: From Craftsmanship to Leverage
AI did not simply make teams faster. It changed where leverage exists.
Large portions of what once justified weeks or months of effort (boilerplate code, repetitive pipelines, standard transformations, and basic analytics) are now automated or heavily assisted. Modern AI systems can generate, refactor, and test code at a pace that far exceeds traditional execution.
This does not eliminate the need for expertise. It concentrates it.
The hardest problems were never about typing code. They were about understanding the business, designing systems that last, managing trade-offs, and ensuring correctness under real-world conditions. AI accelerates execution, but it amplifies mistakes just as quickly.
Hourly pricing was designed to measure effort. AI maximizes leverage. That mismatch is the core tension shaping modern services.
Why the Hourly Model Breaks Down Today
As delivery timelines compress, time-based pricing loses its ability to represent value accurately.
Under an hourly model:
- Efficiency is penalized rather than rewarded
- Automation reduces revenue instead of cost
- Better tools create uncomfortable pricing conversations
- Incentives subtly favor longer delivery over faster outcomes
Even when everyone acts in good faith, friction emerges. Customers struggle to reconcile large invoices with short timelines. Service providers struggle to justify pricing when AI performs much of the mechanical work.
The issue is not trust. It is misalignment.
Data, AI, and the Snowflake Effect
This misalignment is most visible in data and AI work, particularly within the Snowflake ecosystem.
Snowflake is not just a data warehouse. It is a data and AI platform where ingestion, governance, analytics, machine learning, and agentic workflows converge. Because everything operates in a single environment, the distance between idea and execution is dramatically shorter.
As a Snowflake partner, we see this daily. Business users interact with governed data through natural language. AI-powered workflows operate continuously. Consumption-based economics make usage and impact visible in near real time.
In this context, hours become irrelevant. What matters is impact:
- Did reporting cycles collapse from weeks to minutes?
- Did financial reviews stop being manual bottlenecks?
- Did teams move from exporting spreadsheets to operating directly on trusted data?
Snowflake makes outcomes measurable, which is precisely why time-based pricing breaks down so quickly on the platform.
The Rise of the AI Solution Engineer
As execution becomes automated, the role of the engineer evolves.
The modern AI solution engineer is not defined by how much code they write by hand. They are defined by how well they orchestrate systems.
Their responsibilities include:
- Understanding what AI-generated code is doing
- Guiding and constraining agents appropriately
- Ensuring business rules, security, and governance are enforced
- Designing systems that can be monitored, audited, and improved over time
This role demands deep experience. AI removes low-leverage work, but it raises the bar for judgment, accountability, and system thinking.
Outcome-based models make this role visible. Customers are no longer paying for keystrokes. They are paying for expertise applied where it matters most.
Why We Built Viewnear Around Outcomes
Building exclusively on Snowflake influenced this decision directly. Snowflake's architecture rewards clarity over effort. When data models, security, and AI capabilities are centralized, value comes from making the right design decisions, not from repeating work across tools.
From the beginning, we chose not to sell hours. We chose to stand behind outcomes.
That decision also shaped how we staff and deliver work.
At Viewnear, we operate using a flex-capacity model. We do not ask how many full-time engineers a project needs. We define the outcome, then design the delivery backwards. We determine the exact mix of expertise required at each stage, the human roles that must intervene, and the AI agents that should execute. This is not a staffing exercise. It is a systems design decision.
We establish upfront:
- The architectural decisions that must be owned by humans
- The points where judgment and domain expertise are non-negotiable
- The areas where AI agents can safely and efficiently execute at scale
From there, we define the investment and total cost of ownership early, tied directly to outcomes. Customers see the economic shape of the engagement from the start, without abstraction through headcount or time.
Delivery happens through flex capacity. Roles enter and exit exactly when their expertise creates the most leverage. Architects lead early. AI solution engineers orchestrate continuously. Domain experts intervene when business rules and risk matter most.
We deliberately move away from selling named, fully allocated engineers. That model optimizes for utilization, not results. Instead, we deliver a coordinated system of human expertise and AI working together. This produces stronger outcomes, higher quality decisions, and a level of collective intelligence that static staffing models cannot match.
Few services firms are willing to state this plainly, because it places responsibility for outcomes squarely on the provider. That responsibility is exactly where we choose to operate.
What Outcome-Based Services Really Require
Outcome-based services are not cheaper services. In many cases, they require more senior expertise and tighter collaboration.
They demand:
- Clear definition of business problems
- Explicit, measurable success criteria
- Thoughtful system design
- Strong data governance and security
Work is delivered in focused phases: a data foundation, an analytics layer, an AI-enabled workflow. Each phase has a clear outcome and a clear finish line.
This approach removes ambiguity. Customers know what they are paying for. Service providers know what they are accountable for.
Risk, Responsibility, and Trust
Outcome-based models shift responsibility toward the service provider.
If priorities change, data quality is poor, or adoption stalls, the partner feels it immediately. That risk must be managed through structure, milestones, and continuous alignment.
We believe this is appropriate. If expertise is the product, accountability should come with it.
Hourly pricing spreads risk quietly over time. Outcome-based pricing makes it explicit.
The Future of Services
AI will continue to compress execution time. Agentic systems will mature. Automation will remove even more friction.
As this happens, the value of services will increasingly come from judgment, orchestration, and outcomes.
Charging by the hour made sense when value was created through manual craftsmanship over time. Today, value is created through leverage, clarity, and results.
Services are not becoming less valuable. They are becoming more strategic. The future belongs to teams willing to price for outcomes, take responsibility for results, and align themselves with how value is actually delivered.
That is the model we are building at Viewnear.
