# JotVision: full site text Source: https://jotvision.com Updated: 2026-10-14 --- Page: Home URL: https://jotvision.com/ # The system of action for your data and operations. JotVision runs the critical workflows between your ERP, files, and teams. Agents do the routine. Your people decide. Book an intro call Explore Systems of record: Hold the data. ERP, CRM, files, portals, email. Nothing to replace. System of action: JotVision: Runs the work. Agents and operators execute the workflow across your systems. Your people: Decide. Exceptions arrive with the evidence. Results land in your ERP. ## Two operations. One approach. Data comes from your systems or from the physical world. Either way, agents do the routine, your people decide, and the result lands in your systems. Data operations ### Workflows across your teams, ERP, files, communication channels, and external systems Supplier price changes, rebate claims, pricing and margin, and any workflow like them. Commonly used by distributors, manufacturers, and industrial suppliers. - Starts from an export you already produce - Nothing changes in your ERP on day one - Run by our team and agents, decided by yours Explore services How it works Vision & Robotics ### Agentic Visual Applications: cameras and robots that turn the physical world into data and action Operating rooms, labs, warehouses, and inspection lines. Describe what matters, and AVA observes, records, and acts. With PTZOptics and Trossen Robotics. - Natural-language intent, no fixed taxonomy - Local or cloud processing - A person always sets the intent and approves the action Explore AVA Robotics Supporting data workflows for customers and partners ## What we did for AFS Since 2025: automated pricing and sales operations, and delivered an e-commerce channel that fits how their customers actually buy, on a very tight deadline. "We had a ridiculously tight timeline for launching this solution and JotVision was the only business I could trust in meeting our specifications and our deadline, both of which they did." Mona Sabet, SVP Strategy, Programs and Operations, AFS Not consultants"Unlike consultants, they are practical-minded operators. They helped us address several pain points in our pricing and sales operations by simplifying and automating processes, reducing the significant manual effort previously spent on those tasks." Messy data, handled"They had to work through large, complex and often incomplete datasets, and helped us validate the data. They discovered many inconsistencies in our processes and data that they identified and helped us resolve. This reduced the workload on our internal teams." Recommendation"I would recommend Soren, Etay, and the JotVision team to organizations looking for a technology partner that can understand their business, work across complex systems and data, and take ownership of delivering practical and reliable solutions." ## The data and workflow problems we solve. Work that sits between your files, your systems, and your margin, and is done by hand today. This is where we start most often. Our technology is built for any workflow like them. The pricing manager ### Supplier price changes Price files arrive as Excel, PDF, EDI, and portal exports. Someone keys them into the ERP, late and with errors. What we do Validate every change against contracts and margin floors, load it into the ERP, send the exceptions to a person. The rebate analyst ### Rebate claims and credits Eligibility is tracked by hand, claims are filed late, and denied claims are abandoned for lack of time. What we do Track eligibility continuously, file claims on time, and follow up on denials. The commercial director ### Pricing and margin Cost changes reach the sell price weeks later, if at all. Margin leaks between supplier update and customer quote. What we do Move sell prices with cost under your rules, and show where margin is leaking. The product data manager ### Data cleaning and catalog cross-reference Supplier, manufacturer, and internal catalogs use different part numbers, descriptions, and units. Duplicates and mismatches pile up in the ERP. What we do Clean and normalize product data, match items across catalogs, and send uncertain matches to a person. Your workflow ### A problem that is not on this list? If it crosses systems, needs people to interpret rules and has a number to measure, we build a workflow for it on our technology and run it with you. It starts with one workflow and one export you already produce, run beside your team and compared line by line. Book an intro call See our services ## Governance and control, built in. You stay in control in every phase. These are the commitments behind every workflow we run. ### Nothing changes on day one We start from an export you already produce. Nothing is written to your ERP until you say so. ### Access you approve We work through files, exports, APIs, or the interfaces you already use, with the access you approve. ### Every action logged Each update is checked, logged, and measured against your baseline. You see what ran, what was flagged, and what changed. ### Decision rights you set Decision rights are written into every workflow. Nothing goes live without your sign-off. ## You get the founders, not a help desk. Three operators with thirty-plus years each. They learn your business, sit with your team, and own the result. ### Soren Harner Integrations and technologies Systems integration, data science, and workflow automation. Led engineering and product at MuleSoft, Atlassian, BigCommerce, and Meta Company. M.S. in AI from Stanford; 3 patents. ### Etay Gafni Product and experience Workflow analysis, user experience, and product design. Led UX and technology innovation at SAP, then founded BrightAct, a product agency for MuleSoft, Gong.IO, and SanDisk. 3 patents. ### Art Muir Hardware and robotics Robotics, electromechanical systems, and new product introduction. Built hardware at PyrAmes, Artificial Muscle, and Parker Hannifin. BS in Mechanical and Civil Engineering, UC Davis; 10 patents. MuleSoftAtlassianSAPBigCommerceMeta CompanyVignetteSanDiskGong.IOModel NSaverLife30+ years each About the team ## Frequently asked questions Q: Who is JotVision for? Distributors, manufacturers, and industrial suppliers, and the finance and operations leaders who run work across several systems. Pricing, rebates, and margin are the most common starting points, not the only ones. Most of our customers are mid-market companies with an ERP that is not going anywhere. Q: Do we have to change our ERP? No. On day one nothing changes in your ERP. We start from an export you already produce, run the workflow alongside your team, and only write back into your systems when you decide we should. Q: How do we stay in control of what the workflow does? Decision rights are written into every workflow. We work with the access you approve, every update is checked and logged, and nothing goes live without your sign-off. Q: How is this different from an AI tool or a consultant? You do not get a tool to learn or a plan to execute. You get the founders and their agents running the workflow, with your people making the decisions that need judgment. ## Supervised workflows that run themselves. Your systems hold the data. Your people do the work between them by hand. JotVision turns that into an automated workflow, run for you, with your team deciding what matters. Bring one of yours to a 30-minute call. Book an intro call --- Page: Services URL: https://jotvision.com/services # Your workflows, run end to end. Each one starts from a file or system of record you already have and ends in your ERP, with your rules applied and your people deciding the exceptions. Book an intro call See how it works ## How we engage Three phases, one team. The same people who discover the workflow build it and manage the team that runs it. Discovery ### Map the workflow We listen to your team and watch the workflow as it runs today. Then we propose improvements that use technical capabilities you have not tapped yet. Implementation ### Build and prove it We build the workflow with AI agents and test it against your past data until the results match your team's needs and current logic. Then we lock it for runtime, supervised by operators. Operation ### Run, supervise, adapt We run the workflow and supervise every cycle. We handle exceptions and edge cases, and adapt the workflow as your team gives feedback. Governance and control ### You stay in control in every phase. The same commitments apply to every workflow we run. - Nothing changes on day one. We start from an export you already produce. - Access you approve. Files, exports, APIs, or the interfaces you already use. - Every action logged. You see what ran, what was flagged, and what changed. - Your sign-off. Nothing goes live until you approve it. ## Workflow services Where manual work between systems costs the most today. These are the workflows we run most often, not the limit of what we take on. ### Supplier price changes Dozens of suppliers, each sending price lists in their own format: Excel, PDF, EDI, portal downloads, email attachments. The pricing team keys changes into the ERP by hand. At thousands of changes a month, errors and delays are built in. ExcelPDFEDIPortalsEmailERP - We readEvery file, in any format, and match items to your ERP records. - We checkEach change against supplier contracts, cost history, and your margin floors. - We loadApproved changes into the ERP, with a log of every update. - You decideThe held rows: margin below floor, unknown items, suspicious jumps. Each arrives with the evidence. Example: one supplier price runDone In Excel, PDF, emails, documents 2,184 price records Verified and updated ERP, P21, CRM, Zendesk Power BI, Teams, email Updated automatically: 2,131 Held: margin below floor41 Held: item not in ERP12 53 for your review, each with the record, the contract clause, and a recommendation. ### Rebate claims and credits Rebate programs have conditions spread across agreements, purchase history, and supplier portals. Eligibility is tracked in spreadsheets, claims are filed late, and denied claims are written off because nobody has the time to appeal. AgreementsPurchase historySupplier portalsERP - We trackEligibility continuously against the terms of each program. - We fileClaims assembled from your data and submitted on time, in the supplier's format. - We follow upDenials are investigated and appealed with the supporting records. - You decideDisputed amounts and anything outside the agreed terms. ### Pricing and margin Cost changes land in the ERP but sell prices move weeks later, if at all. Margin leaks between the supplier update and the customer quote, and nobody can see where. CostPrice listsCustomer agreementsERPE-commerce - We applyYour pricing rules so sell prices move with cost, by customer group and product line. - We flagItems selling below target margin and the reason. - We publishUpdated prices to the ERP, price lists, and e-commerce where you use it. - You decideStrategic exceptions: key accounts, promotions, competitive moves. ## Is your workflow a fit? The services above are where we start most often. Any workflow with these four traits is a candidate, and we build it on the same technology. ### Crosses systems It needs data or action in more than one place: ERP, files, portals, email. ### Needs interpretation People apply contracts, policies, history, or thresholds to decide what happens. ### Heavy on exceptions The happy path is easy. The cost is in the unusual cases and the incomplete data. ### Has a clear cost/value Hours saved, margin recovered, days to credit, error rate. Something to measure against. Common next workflows ### Finance reconciliation Cash application, invoice matching, exception resolution. ### Supplier and customer onboarding Data collection, validation, and setup across systems. ### Compliance evidence Collecting records, applying policy, preparing reports. ### Order and quote handling Validating orders against contracts, stock, and pricing. ## Frequently asked questions Q: Which industries do you work with? Mostly distributors, manufacturers, and industrial suppliers in the mid-market, where pricing, rebates, and margin run across an ERP, supplier files, and portals. Q: Do you need clean data first? No. Supplier files are messy and ERP records are incomplete. The workflow is designed around that reality, and the inconsistencies we find are reported back to you. Q: Can you work with our ERP? Yes. We work through files, exports, APIs, or the interfaces you already use, with the access you approve. We have worked with legacy and modern ERPs, SaaS tools, portals, and EDI. Q: What if our workflow is not one of these? If it crosses systems, needs people to interpret rules, is heavy on exceptions, and has a measurable outcome, it is a good fit. Finance reconciliation, supplier onboarding, and compliance evidence are common next steps. ## Which workflow is costing you most? Pricing, rebates, margin, or something else entirely. Tell us on a 30-minute call. We will ask for one export and come back with a line-by-line comparison. Book an intro call --- Page: How It Works URL: https://jotvision.com/how-it-works # Agents do the routine. Your people decide. Your systems hold the data. The work happens between them. Here is how JotVision runs it, and where your team stays in control. Book an intro call ## How information flows Data from your systems feeds the agents. Agents do the work and hand exceptions to people. What people decide is fed back so the agents handle it next time. Your systems of record ### Messy by default ERP, portals, files, email, legacy, and SaaS. Nothing to replace. ERPCRMSaaSDatabasesLegacyPortalsFilesEmail Data and context Agents ### Do the work - Assemble the context each step needs - Execute routine work end to end - Flag what needs judgment Completed work Outcome ### Measurable value - Cycle time - Accuracy - Throughput - Margin and risk Measured against your baseline. Exceptions escalated Agents updated Case and history Human in the loop ### People own the outcome - ReviewThe exception arrives with full context - ResolveA person decides and closes the case - TeachThe rule is added so agents handle it next time Resolved cases ## One workflow, step by step. A supplier pricing change, from the file arriving to the ERP being updated. ### Supplier input New pricing arrives as a file, email, portal download, or feed. Arrives as FileEmailPortalFeed ### Context The relevant supplier, customer, product, and agreement data is gathered. Reads from ERPCRMContractsFiles ### Reconcile Existing ERP and operational records are checked and reconciled with the file. Checks ERPDatabasesLegacy ### Your rules Rules, thresholds, and history determine what can proceed automatically. Applies RulesThresholdsHistory ### Human judgment Only exceptions and approvals reach a person, with the context to decide. Reaches a person ExceptionsApprovals ### Action Approved changes are written to the right systems. Updates ERPCRMPrice listsPortal ### Verify The outcome is checked, logged, and measured against the baseline. Records CheckedLoggedMeasured ## How we work with you A loop, not a hand-off. Each cycle makes the workflow faster, more accurate, and cheaper to run. Discovery ### Map the workflow We listen to your team and observe the workflow as it runs today: systems, rules, exceptions, and the baseline for time, accuracy, and margin. Then we propose improvements using capabilities you have not tapped yet. Implementation ### Build and prove it We build the workflow with AI agents around your existing systems and test it against your past data until results match your team's logic. Then we lock it for runtime, supervised by operators. Operation ### Run, supervise, adapt Agents and our operators run the workflow. We handle exceptions and edge cases, measure against the baseline, and adapt as your team gives feedback. You get results, not a queue. Operation feeds back into Discovery. Each cycle finds the next improvement, and what worked moves to the next workflow. ## You decide where automation ends and people begin. Decision rights are written into every workflow, so each action has a defined level of authority. Execute ### Known work proceeds Policy-compliant, routine work runs automatically and is logged. Review ### Exceptions arrive ready to decide A person receives the case with the context required to decide quickly. Approve ### High-impact actions wait Consequential changes need explicit authorization before anything is executed. ## Who owns what You own - The business outcome and the policies behind it. - Consequential decisions, with context and a recommendation in hand. - Your systems of record. We work through the access you approve. We own - Execution of the agreed workflow, end to end. - Monitoring, maintenance, and improvement of the agents. - Defined exceptions, resolved within documented decision rights. ## Built so you can trust it with real work ### Nothing to rip out Your systems of record stay. We work through the access you approve. ### No clean-data project first We work around imperfect data and report what we find. ### Every action on the record Logging, approvals, and changes stay reviewable and reversible. ### No platform to administer The deliverable is the outcome, not another application for your team. ## Frequently asked questions Q: What is a system of action? The layer that carries a workflow to completion across your existing systems. It gathers context, reconciles data, applies your rules, handles exceptions and approvals, updates the right systems, and verifies the result. Your ERP and CRM remain the systems of record. Q: Where do people stay involved? Every workflow has written decision rights. Routine, policy-compliant work proceeds automatically. Exceptions reach a person with full context. High-impact actions wait for explicit approval. Q: Who runs it day to day? JotVision does. We monitor the agents, resolve defined exceptions within the agreed decision rights, and bring your team only what needs their judgment. Q: How is this different from integration, RPA, or an AI assistant? Integration moves data. Assistants give answers. RPA follows a fixed script. JotVision carries the whole workflow to an outcome, including the exceptions, and a team owns the result. ## See it on your own data. One export from you, a line-by-line comparison from us. Nothing changes in your ERP until you say so. Book an intro call --- Page: AVA URL: https://jotvision.com/ava # Turn what happens in the physical world into data and action. AVA, Agentic Visual Applications, gives JotVision visual understanding of physical environments. Describe what matters in natural language, and AVA can observe the scene, identify relevant objects and events, create structured data, and trigger the workflow that should happen next. SeeUnderstandRecordAct Book an intro call From observation to action Computer vision ### Detects what is visible Finds objects and motion in an image. AVA ### Understands what matters Interprets the scene in the context of your stated intent. JotVision ### Turns it into action Combines it with enterprise context and carries the workflow to completion. ## Some of your most important data doesn't exist in a system yet. It exists in rooms, equipment, procedures, interactions, objects, and events. 1 ### Objects What is present, missing, moved, or used? 2 ### People Who is present, interacting, or performing an activity? 3 ### Events What happened, in what order, and at what time? 4 ### State What is the current condition of the environment or process? 5 ### Relationships How are people, objects, and events connected? AVA turns these observations into structured context that JotVision can record, analyze, or act on. ## Observe, understand, decide, act. Camera movement and video capture are things AVA can do. They are not what defines it. 1 Observe ### Watch the environment Continuously interpret what is happening in a physical environment. 2 Understand ### Identify what is there Identify relevant objects, people, states, events, and relationships. 3 Decide ### Work out what matters Use the stated intent and operational context to determine what matters. 4 Act ### Carry it forward Create data, capture evidence, notify someone, trigger a workflow, control a device, or request human review. ## Describe what matters. Instead of configuring every workflow around a fixed taxonomy of predefined events, describe the observation or outcome you care about in natural language. "Tell me when this tray is complete." "Track when the patient enters the room and when positioning is complete." "Inspect this instrument for visible damage." "Record when this object is removed and when it returns." "Keep the camera on whoever is demonstrating the procedure." "Alert me if this step is skipped." Intent can change without rebuilding the entire visual application. ## The physical world, connected to action. AVA is not an isolated computer-vision product. It is a source of real-world context for a system of action. Physical world ### Where it happens PeopleObjectsEquipmentRoomsProcessesEvents AVA ### Sees and structures - Observe - Understand - Structure context JotVision system of action ### Decides and executes - Apply rules - Combine with enterprise data - Determine next action - Escalate if needed - Execute workflow Outcome ### What gets done RecordNotifyUpdate systemTrigger processControl deviceCreate evidenceRequest approval ## Visual context is more useful when combined with business context. AVA does not operate only on pixels. JotVision can combine what AVA observes with enterprise context. AVA sees ### Instrument placed on table + Your ERP and operational systems know - Which procedure - Which tray - Which instrument should be present - Which staff member owns the workflow JotVision can determine ### Whether something is missing, unexpected, or requires action System of actionRecordEscalateUpdateNotifyRequest review An illustrative example. The specifics adapt to each validated use case. ## AVA in practice Example applications across use cases. Each turns what the camera sees into data, evidence, or action. Observations to data ### Surgical instrument tray identification Point AVA at a tray and it identifies each instrument by manufacturer and part number, matched to catalog reference images. What was a manual count and check becomes a record. - Each instrument tagged on sight - Matched to the catalog entry - Powered by LayerJot Inspection ### Robotic visual inspection Cameras on robotic arms examine each instrument from every angle and return a result, with the evidence attached for review. - Surface wear and tear - Mechanical damage and alignment - Rust, corrosion, pitting, and tint OR.FLOW ### Operating room flow analysis AVA watches the room and logs what happens: staff and patient detected, room entry, patient transfer, and positioning, with identities blurred. You get a notification when the report is ready. - Events detected and timestamped - Identities blurred by default - Report delivered when ready Lecture capture ### Automatic lecture recording A reference camera sees the whole room while the PTZ camera follows what matters. Set a watch list and AVA locks on and frames it, with no camera operator. - Watch list: presenter, whiteboard, projector screen - Locks on and tracks the presenter live - A showcall sequence cuts between subjects ## Use cases, organized by the action they drive. Different environments, one architecture. ### Observe & Measure Understand what is happening in a physical process. Operating-room flowLine sequences ### Inspect & Verify Check objects, conditions, sequence, or completeness. Instrument tray IDRobotic inspection ### Track & Record Create structured records of physical events. Room eventsLecturesProcedures ### Guide & Control Use visual understanding to influence cameras, devices, or workflows. PTZ trackingRobotic arms ### Trigger & Escalate Start a business process when a real-world condition occurs. Skipped-step alertReview request ## What AVA produces From what the camera sees to data you can act on. Structured data ### Observations become usable data Where permitted and appropriate: - Objects - Identities - State - Timestamps - Counts - Sequences - Events - Measurements Evidence ### Visual context behind the result So a result can be reviewed, not just trusted: - Images - Video clips - Event history - Timestamps - Relevant scene context Action ### Observation drives the next step AVA does not stop at detection: - Update a record - Trigger a workflow - Notify a person - Escalate an exception - Control a camera or compatible device - Request approval - Create a task ### Privacy built in Faces and identities can be blurred in the analysis, so the data is useful without exposing people. ### Local or cloud processing Process footage and prompts on your premises or in the cloud, whichever fits your requirements. ### An API is on the way We are working to open an API so you can build on AVA’s scene understanding. Talk to us about early access. ## AVA can also control how the scene is captured. Video and PTZ control are examples of actions AVA can take once it understands the scene. ### Follow a person or object Lock on and re-acquire through movement and occlusion. ### Maintain framing Keep the subject framed as the scene changes, with no operator in the room. ### Switch viewpoints Move between subjects, such as presenter, whiteboard, and screen. ### Control compatible PTZ cameras Direct PTZ cameras from a stated intent, in plain language. ### Capture event-specific video Record the moments that matter, wide context and close-up detail in sync. ### Create review-ready records Paired assets ready for training, inspection, QA, and incident review. Also in Vision & Robotics ## From seeing to doing. Cameras on robotic arms let AVA examine, verify, and respond to physical objects, with a person reviewing what matters. Explore robotics ## Partners in the physical world. AVA works with proven hardware and specialist technology partners, so the cameras and catalogs are theirs and the intelligence is ours. Camera partnerPTZOptics Professional PTZ cameras, controllers, and software for broadcast, education, healthcare, and manufacturing. AVA directs PTZ cameras to frame what matters. Visit PTZOptics Customer & technology partnerLayerJot Powers instrument identification and the catalog matching behind AVA's instrument tray application. Visit LayerJot ## Frequently asked questions Q: What is AVA? AVA stands for Agentic Visual Applications. It is the visual intelligence layer of JotVision’s system of action. It observes a physical scene, identifies relevant objects, people, states, and events, creates structured data and evidence, and triggers the workflow that should happen next. Q: How is AVA different from computer vision? Computer vision detects what is visible. AVA understands what matters in the context of your stated intent, and JotVision turns that understanding into action. Q: How do I tell AVA what to look for? In natural language. Describe the observation or outcome you care about, such as when a tray is complete or when a step is skipped. Intent can change without rebuilding the visual application. Q: Can AVA use my business data as well as video? Yes. JotVision can combine what AVA observes with enterprise context from your ERP and operational systems, to determine whether something is missing, unexpected, or needs action. Q: Where is video processed, and what about privacy? Footage and prompts can be processed locally on your premises or in the cloud, depending on your requirements. Faces and identities can be blurred in the analysis. Q: Which hardware does AVA work with? AVA works with compatible PTZ cameras, including PTZOptics, and with robotics hardware such as Trossen Robotics arms for robotic visual inspection. Q: Can I build my own applications on AVA? Not yet. We are working to open an API so you can build on AVA’s scene understanding, tracking, and event detection. Talk to us about early access. ## Show us a scene worth acting on. Tell us what AVA should see and what should happen next: instrument checks, inspection, lecture capture, room analytics, or an application of your own. We will walk you through a live demo. Book an intro call --- Page: Robotics URL: https://jotvision.com/robotics # From seeing to doing. Cameras on robotic arms let AVA examine, verify, and respond to physical objects. Inspection, identification, and handling, with evidence attached and a person reviewing what matters. Book an intro call About AVA, the vision layer ## Robotic visual inspection. The same vision layer that watches a room can direct an arm, check an object, and record the result. ### Visual understanding becomes motion and results Robotic arms position cameras at every angle of an object. AVA reads what it sees, returns a result with the evidence attached, and routes anything uncertain to a person. The same loop can guide a robot or device to its next step. 1 ### Look Cameras on robotic arms examine an object from every angle. 2 ### Decide AVA applies your intent and the operational context to what it sees. 3 ### Act Return a result, trigger a workflow, or direct a compatible robot or device. 4 ### Verify Evidence is attached and exceptions go to a person for review. ## Where it applies Any task where an object has to be looked at closely, compared to a standard, and either passed or routed to a person. ### Instrument and tool inspection Verify identity, condition, and completeness of surgical instruments, tools, and kits before they go back into use. ### Incoming goods and parts Check received items against the order and the catalog, flag damage or mismatches, attach the photos. ### Quality at the line Examine finished parts from every angle against your acceptance criteria and keep the evidence for each decision. ## Partners in the physical world. AVA works with leading hardware makers, so the cameras and robots are proven and the intelligence is ours. Camera partnerPTZOptics PTZOptics Professional PTZ cameras, controllers, and software for broadcast, education, healthcare, and manufacturing. AVA directs PTZ cameras to frame what matters. Visit PTZOptics Robotics partnerTrossen Robotics Trossen Robotics Hardware and data backbone for Physical AI: robot arms, mobile platforms, and teleoperation tools that work together out of the box. A foundation for robotic visual inspection and physical workflows. Visit Trossen Robotics LayerJot ### LayerJot Powers instrument identification and the catalog matching behind AVA's instrument tray application. Customer & technology partner ## Autonomy with a human in charge ### Bounded by intent People define what to inspect and what passes. The robot never widens its own brief. ### Evidence on every result Each pass or hold carries the images and the reasoning, so it can be audited later. ### Exceptions to a person Anything uncertain stops and waits for review. Nothing is discarded or forced through. ## Bring a physical workflow worth automating. Book an intro call --- Page: About URL: https://jotvision.com/about # Operators, not a software vendor. You are not buying a platform, a tool, or an AI agent interface. Work directly with Soren, Etay, and Art. Three operators who learn your business, sit with your team, and own the result. Book an intro call ## The team Three founders with thirty-plus years each of building and running enterprise software. ### Soren Harner Integrations and technologies Systems integration, data science, and workflow automation. Led engineering and product at MuleSoft, Atlassian, BigCommerce, and Meta Company. M.S. in AI from Stanford; 3 patents. ### Etay Gafni Product and experience Workflow analysis, user experience, and product design. Led UX and technology innovation at SAP, then founded BrightAct, a product agency for MuleSoft, Gong.IO, and SanDisk. 3 patents. ### Art Muir Hardware and robotics Robotics, electromechanical systems, and new product introduction. Built hardware at PyrAmes, Artificial Muscle, and Parker Hannifin. BS in Mechanical and Civil Engineering, UC Davis; 10 patents. MuleSoftAtlassianSAPBigCommerceMeta CompanyVignetteSanDiskGong.IOModel NSaverLife30+ years each ## On the floor with customers. Before JotVision, the founders built and ran products at MuleSoft, Atlassian, and SAP, the plumbing that connects enterprise systems. JotVision applies that experience to the work between your systems: start with the real workflow, run it, and only then talk about software. ### We learn your business first We sit with the team doing the work before we automate any of it. ### We run it, not just build it Monitoring, exceptions, and improvement stay with us. ### We work in your environment Hybrid, legacy, imperfect data. That is the normal case. ### Adoption is part of the job Technology only counts if your people actually use it. ## What a customer says "We had a ridiculously tight timeline for launching this solution and JotVision was the only business I could trust in meeting our specifications and our deadline, both of which they did." Mona Sabet, SVP Strategy, Programs and Operations, AFS ## Talk to the people who will do the work. A 30-minute call with a founder. Bring the workflow that costs you most. Book an intro call