ICTWEEK · TashkentMeet us at the event →

Technical presales automation

More projects move forward. The same engineering team.

Way2Sol helps turn customer emails, documents and infrastructure exports into architecture options, calculations and a draft proposal, using your company’s engineering rules.

Presales leads the project. Architects focus on complex questions and design decisions.

Discuss a pilot See how it works

Customer materialsArchitecture optionsTraceable calculationsEngineer review

TEAM PROJECTSTechnical presales

in progress

4active projects

1waiting for data

1needs an architect

SELECTEDVirtualization platform upgrade

Example project

▶

From request to proposal

One request changes the architecture.

‘Add a cloud email archive.’ That one line changes the deployment, licensing and scope of work.

Customer request

‘Move email archives to the cloud. Keep the primary mailboxes here.’ In this example, Exchange runs on premises, with no hybrid deployment or directory synchronization to Microsoft 365 yet.

Dependencies

Way2Sol maps the requirement to the changes it needs: an Exchange hybrid deployment, directory synchronization and cloud archiving rights. Server versions, access methods and customer constraints are checked.

Scope and cost

The proposal adds hybrid configuration, directory synchronization and archive provisioning. License selection accounts for existing entitlements. Cloud storage approval and any server infrastructure changes remain open for review.

Ready for approval

The architect receives the before-and-after design, changes to scope and cost, risks and open questions. Once approved, Way2Sol prepares the proposal with the chosen architecture, licenses and delivery plan.

How work changes

Less manual work from the first request to the proposal.

Reviewing documents, gathering requirements and running calculations take time before architecture work even begins. Way2Sol handles repetitive tasks so your team can move on to discussing the solution.

01 · SALES

Shares customer materials

Emails, notes, documents, spreadsheets and infrastructure exports. Start with the materials your team already has.

02 · WAY2SOL

Prepares a draft proposal

Organizes requirements, identifies missing information and prepares questions, architecture options and calculations using company rules.

03 · PRESALES

Leads the project

Reviews calculations, clarifies requirements with the customer and prepares the proposal for approval.

04 · ARCHITECT

Chooses the technical approach

Compares options, addresses unusual constraints and approves complex design decisions.

What your team getsRequirements, architecture options, calculations and open questions stay together. When source data changes, the team can see which calculations and proposal sections need updating.

01Customer requirements

Objectives, constraints and infrastructure details gathered from correspondence, documents and technical exports.

02Questions to clarify

Missing or conflicting information collected into questions your team can discuss with the customer.

03Architecture options

Suitable options with calculations and constraints to compare, including an upgrade to the current platform.

04A draft proposal

Components, resources, licenses, risks and a delivery plan, linked to the source data used in the calculations.

Less time assembling documents and repeating calculations. More time for the customer’s requirements and the quality of the solution.

Technology packs

Engineering knowledge for key technologies

Each pack brings together design rules, calculations, licensing and reference architectures for its technology area. Industry practices and vendor guidance are combined with your engineers’ methods and kept as rules that apply to every new project.

Ready for a pilot

readiness100%

Microsoft Exchange

Email infrastructure: architecture, resources, archiving, licensing and migration.

readiness95%

Microsoft Core Infrastructure

Active Directory, DNS, DHCP and file services: dependencies, high availability and resource sizing.

readiness85%

Networking and security

Topology, segmentation, network and security equipment selection, placement dependencies.

readiness80%

Hyper-V

Windows Server virtualization: clusters, storage, high availability and licensing.

readiness70%

VMware vSphere

Virtualization: clusters, resource sizing, compatibility, licensing and migration.

readiness70%

Proxmox VE

Virtualization: clusters, compute resources, storage and migration from other platforms.

readiness65%

OpenStack

Cloud infrastructure: service selection, role placement, resources and high availability.

readiness60%

Backup · Veeam

Backup strategies, repositories, retention, recovery and licensing.

In progress

readiness30%

Databases

Database placement, resource sizing, high availability and storage requirements.

readiness20%

DR / BCDR

Disaster recovery: RPO/RTO targets, recovery sites, service dependencies and failover plans.

In developmentservers and storage

The knowledge is available when the expert is away.Colleagues continue with documented methods and design decisions, while an architect reviews unfamiliar requirements.

Example project · illustrative data

VMware, 8 hosts, 214 VMs. Which upgrade path fits best?

A customer wants to upgrade its virtualization platform. In this example, the team clarifies requirements, compares three options and chooses a migration approach.

VM-024 · STAGE 01

What is known and what needs clarification

The customer’s email, sales notes and infrastructure export are gathered in one project. Acceptable downtime is still unknown, so the team needs to ask the customer.

Data and questionsprepared

018 ESXi hosts, 214 VMsconfirmed

02Usable capacity: 74 TBconfirmed

03Acceptable downtimeask customer

VM-024 · STAGE 02

Three approaches to the platform upgrade

Upgrade the existing platform, move to a different one or migrate workloads in stages. The team compares resource requirements, constraints and risks for each option.

Optionsprepared

01Keep and upgradeoption A

02Move to another platformoption B

03Migrate workloads in stagesoption C

VM-024 · STAGE 03

Resources and constraints for each option

The engineer can inspect the parameters and assumptions behind each calculation. Critical systems need a separate compatibility check before the platform is selected.

Calculations and risksprepared

01Compute resourcescalculated

02Storage requirements1 assumption

03Critical VM compatibilityreview

VM-024 · STAGE 04

The architect chooses the migration approach

The options, calculations and open questions are ready to review. The architect selects the target platform and decides how to migrate systems with special requirements.

Architect reviewawaiting approval

01Target platformselect

02Legacy system migrationapprove

03Migration plan and proposalprepare

Source data and open questions stay with the project

Reviewing calculations

Calculations your team can verify.

Each calculation includes its inputs, sources and assumptions. The engineer can see what is confirmed, what needs clarification and which parameters require approval.

Confirmed by a source Assumption Needs clarification Requires approval

Storage · option Bsource data

Usable capacity: 74 TBCustomer infrastructure export

confirmed

Growth allowance: 25%Preliminary value used for sizing

assumption

Acceptable latency for critical systemsNeeds clarification from the customer

request

ARCHITECT APPROVALPlacement of systems incompatible with the new platform

Team

Who builds Way2Sol.

Three people with an engineering background: large integration projects, banking platforms and internal enterprise tools. The calculation core and the packs are written by people who have designed and delivered such systems themselves.

01 · Product and architecture

DmitryProduct, architecture, methods

Twenty years in large integration projects, from architecture to heading development. Led the development of a unified information space for a world-class international sporting event; built national-scale integrations on IBM WebSphere, Oracle and BizTalk. At Way2Sol he owns the engineering project model and the rules in the packs — what makes the calculations verifiable.

AWS Solutions Architect – Associate · MCSA

02 · Calculation core

IlyaCore and data

Head of analytics platform development at a major bank. Writes the calculation core: rules, data dependencies, calculations and their traceability. Owns the Databases pack.

Oracle Certified Developer

03 · Platform and quality

AndreyPlatform, Product Packs, testing

Full-stack developer of enterprise tools. Writes the technology packs and the interface, runs the demo environments and owns testing — the regression scenarios that check system behaviour from source data to the final document.

Full-stack · DevOps · QA

Distributed teamLegal entity to be set up for the first pilot

A pilot with your team

Put Way2Sol to work on one of your projects.

We’ll help choose a completed project and agree what to compare. We’ll work from the original materials to a proposal. Your engineer can assess the calculations, architecture options and revisions needed.

Arrange a meeting

01Choose a project together

Discuss the task and confirm it is a good fit for the pilot.

02Prepare a proposal

Use the materials your team had at the start of the project.

03Compare with your team’s work

Review calculation quality, proposal completeness and engineering time.

Anonymized materialsNo infrastructure connectionTerms agreed before the pilot

Product questions

Before we get started.

How do engineers and architects use Way2Sol?

Way2Sol helps review source materials and prepare calculations and a draft proposal. The engineer checks the results and clarifies requirements. The architect chooses the technical approach and approves complex design decisions.

What materials do we need?

For an initial conversation, just tell us about your team’s work. For the pilot, we’ll choose a project together and gather its original emails, documents, spreadsheets or infrastructure exports.

How can we check the calculations?

Calculations retain their source parameters and references. Assumptions and missing data are marked separately so the engineer can review the result and request clarification.

Can we compare different vendors?

Yes, where they meet the project requirements and are supported in the pilot. Upgrading the current platform may also be an option. We’ll agree the alternatives with your team.

How do we start a pilot?

Get in touch. We’ll discuss the proposals your team prepares, show you the product and help choose a project to evaluate. Scope, data handling and pricing are agreed before the pilot begins.

↳

Resources