Services · Customer documentation · Automotive suppliers

More time for quality and engineering. The AI agent takes care of the PPAP administration.

A service from Cloudfox for suppliers to the vehicle manufacturers or their tier-1s. The AI agent gathers the documents for every PPAP submission, follows up what is missing and checks everything against the drawing revision and the customer's requirements. You decide and sign the PSW. We are responsible for the agent when it runs. Fixed price.

Faster to an approved submissionAs soon as the part is new or changes, the agent fetches the documents where they are: in your systems and at the sub-suppliers, by email or in their web portals. What is missing is followed up at once, so that the change can go into production sooner.
Hours back in quality and engineeringThe agent does the work: fetches your documents, requests what is missing from the sub-suppliers, checks and reminds. You do what requires judgement: decide on deviations and sign.
Deviations found before the customer finds themEvery document is checked against the drawing and the customer's requirements: right revision, dimensions within tolerance, PSW and IMDS in agreement. What deviates is shown to you at once, not when the customer rejects the submission.
Traceable at the customer's auditThe documents stay where you have them: in SharePoint, the quality system or the ERP. In the browser, with your Microsoft account, every submission is there, searchable, with links to the documents and a locked copy of what was submitted: what, for which revision, when and who approved the deviation.
Book 30 minutes
ERP systems Business Central · Dynamics FO · Monitor · Jeeves · Garp · SAP · M3 · IFS · Visma · QAD · and more
Documents Part Submission Warrant (PSW) · Drawing and engineering change order · Dimensional and test results · Control plan, process FMEA and measurement system analyses · IMDS report · Sub-suppliers' PSW, IATF certificates and substance and conflict minerals declarations · and more, scanned or digital
The problem

The part is ready. The documents are not.

The vehicle manufacturers and their tier-1s approve a new or changed part through PPAP, the German ones through PPF. When the drawing, material, tooling, manufacturing site or sub-supplier changes, the package has to be submitted again. What it contains is governed by the submission level and the customer's own requirements, the IMDS report usually has to be accepted before the PSW is submitted, and what you buy in has to have the sub-supplier's own PPAP and declarations.

Someone has to gather the documents, per part and submission. That means searching the ERP, the quality system, the measuring room's files and the inbox, logging in to the sub-suppliers' web portals and emailing whoever's document is missing or has expired. Then the documents have to be checked against the drawing and against each other, the PSW filled in and the package submitted.

Four things often go wrong.

  1. The submission is late. The documents are not gathered until the date is near. If a document is missing the submission slips, and without an approved PSW the part cannot be delivered in series.
  2. The wrong document goes out. A dimensional report on an older drawing revision, a control plan not updated after the change, or a dimension out of tolerance that nobody had time to see. The customer finds it.
  3. The follow-up is dropped. The sub-supplier does not answer the first email, and the reminder is never sent, because nobody has the time.
  4. The requirements live in someone's head. Which level and which specific requirements each customer has, one person knows. When that person is away, someone else has to guess.

It costs in two ways. First in hours: every submission takes time from the quality engineers, time that would otherwise go to the processes, the audits and the customers' questions, and the hours grow with every new part and every change. Then when the customer finds the error: a submission rejected and redone, a finding at the customer's audit, or a series delivery that has to wait until the PSW is approved.

Today
The documents are gathered by hand, and the errors are found late
Drawing and change orderthe customer's revision D is in the inbox, PDM still has C
Process flow diagramolder version in the project folder, new operation missing
Process FMEAnot updated for revision D
Control planmissing the new dimension in revision D
Measurement system analysistoo old under the customer's requirements
Dimensional reportsearched for in the measuring room's files
Capability studynobody has reminded the metrology technician
Material and performance testschased by email at the sub-supplier and the lab
IMDSthe report applies to revision C, waiting for the sub-supplier
PSWfilled in by hand
Submission to the customeruploaded to the portal by hand, or emailed
With the agent
The agent gathers and follows up, and the errors show at once. You sign
Drawing and change orderfetches revision D from the customer and enters it in your PDM, the design engineer releases it, the agent reminds until it is done
Process flow diagramfetches the current version, if the operations do not match the PFMEA and control plan it reminds process engineering
Process FMEAsees that it is older than the change order, reminds the owner
Control planflags that the dimension is missing, reminds the owner
Measurement system analysissees that it has expired, reminds the metrology technician
Dimensional reportfetches the report for revision D, checks every dimension against the drawing
Capability studyreminds the metrology technician until it is done, checks Ppk against the customer's limit
Material and performance testsrequests from the sub-supplier or the lab and reminds, checks that the lab is accredited
IMDSrequests material data and reminds, checks via IMDS Connect that the report applies to revision D and is accepted
PSWfilled in from the customer's template and checked field by field, you sign
Submission to the customersubmitted in the customer's portal or by email after your signature, and saved per submission
Your signature on the PSWalways, before the submission
Example of a level 3 submission with 10 documents, for a supplier manufacturing to the customer's drawing. Made-up data. Red is an error that slips through, grey is time spent.
What is submitted at each level

The customer sets the level, and the level governs the package. Level 3 is the usual one unless the customer says otherwise.

DocumentLevel 1Level 2Level 3Level 4Level 5
PSWSubmittedSubmittedSubmittedSubmittedReviewed at your site
DrawingKept by youSubmittedSubmittedPer customerReviewed at your site
Dimensional resultsKept by youSubmittedSubmittedPer customerReviewed at your site
Material and performance testsKept by youSubmittedSubmittedPer customerReviewed at your site
Process flow diagramKept by youKept by youSubmittedPer customerReviewed at your site
Process FMEAKept by youKept by youSubmittedPer customerReviewed at your site
Control planKept by youKept by youSubmittedPer customerReviewed at your site
Measurement system analysisKept by youKept by youSubmittedPer customerReviewed at your site
Capability studyKept by youKept by youSubmittedPer customerReviewed at your site
Submitted: sent to the customer. Kept by you: available at your site and shown on request. Reviewed at your site: the customer comes to you and reviews the documents on site. A selection: AIAG's list has 18 elements, among them the customer engineering approval, design FMEA, sample parts and checking aids. Customer-specific requirements (CSR) can change the rows, and the agent reads them per customer. German customers under VDA 2 (PPF) state the scope per part instead of a level, and the cover sheet is the PPF-Deckblatt instead of the PSW. The agent reads the scope from the request in the same way.
Our solution

Four steps, from changed part to approved submission.

  1. We gather the documents. The agent we implement for you reads the level and the drawing revision from the customer's request, in the web portal or the change order, and uses the customer-specific requirements (CSR) we entered per customer in the mapping. Then it fetches the documents where they are: the drawing from your PDM (or PLM), control plan and PFMEA from the quality system, dimensional reports from the measuring room's files, the sub-suppliers' by email or from their web portals. The agent is connected to your ERP and quality system, so that every document lands on the right part, drawing revision and customer. If you manufacture to the customer's drawing, the agent enters the customer's new revision in your PDM and the design engineer releases it. If you own the design, it reads the revision from your own PDM and change process; the DFMEA is yours and is judged by you.
  2. We follow up what is missing. If a document is missing, or has expired, the agent requests a new one from the sub-supplier and reminds until it arrives: their PSW, material data in IMDS, test results or CMRT. The sub-suppliers' IATF certificates are monitored, so that the question goes out before the certificate expires and not when the submission is already waiting. If one of your own documents is missing, such as a control plan not updated after the change or a dimensional report not yet done, it reminds whoever at your company owns it. If the customer has requested a drawing revision that is not in your PDM, the agent enters it as unreleased and reminds the design engineer until it is released, at once and not when the submission is waiting.
  3. We check against the drawing and the requirements. Two levels. The form: right part, right drawing revision, valid, and that the package is complete for the level and the customer's CSR. And the context: the agent compares the documents with the drawing, with each other and with the customer's requirements for the part. The same revision throughout the package, the dimensions against the tolerances, the operations in the flow, PFMEA and control plan, the PSW against IMDS. The PSW is checked field by field, see the example below, and the whole submission against the list after that. In addition, that the sub-suppliers' certificates are valid and that their PSW, ELV and REACH declarations and CMRT exist and apply to the part and the revision. What is measurable the agent judges itself: a dimension out of tolerance, an expired certificate or a revision that does not match is an error, with a reference to where in the document it is found. What it does not do: judge whether the risks in the PFMEA are rated correctly or whether an action is sufficient. That is your engineering judgement, and that is where the hours should go. If everything agrees the agent fills in the PSW from the customer's template and presents it for signature. If something deviates it is shown highlighted, with the document beside it. A person at your company decides and signs. The agent never approves on its own, and if it is unsure about a document it says so.
  4. We submit and save. Once the PSW is signed the package is submitted the way the customer requires – in the customer's web portal, by email, or gathered at your site when the customer reviews on site, as at level 5 – and saved per part and submission. At the customer's next audit the answer is there: what was submitted, for which revision, when it was submitted and who approved the deviation.
Where the documents come from

The agent works in the systems you already have. This is what it looks like for a level 3 submission:

DocumentWhere it isThe agent
Part Submission WarrantThe customer's template, the part in the ERPFills in, you sign
Drawing and change orderThe customer's web portal or change order, your PDMFetches the right revision, enters it in PDM
Process FMEA and control planThe quality system, the project folderFetches and checks the revision
Dimensional report and capabilityThe measuring room's filesFetches and checks against the drawing
Sub-suppliers' PSW and test resultsEmail or their web portalsRequests and reminds
Sub-suppliers' PPAPEmail or their web portals, your requirements per supplierRequests, checks, you approve
IMDSThe files from your IMDS Connect licenceReads the files, requests data and checks the weight
The packageThe customer's web portal, email or at your siteSubmits after your signature
Example. Which systems apply at your site we go through in the mapping.
Following up the sub-suppliers

When a document is missing or has expired the agent requests it in your name and follows up until it arrives. The intervals are set per supplier.

  1. Day 0RequestEmail in your name: the missing document, part, submission and the date it is needed.
  2. Day 4ReminderThe same request, with what is still missing.
  3. Day 8Reminder with the buyer in copyThe person who owns the supplier relationship sees that it is taking time.
  4. As the submission date approachesThe question to you in TeamsWait, or submit with an open item and request interim approval. You decide.
Every request, reminder and reply is saved on the submission.
The PSW, field by field

Part 7714 for Nordhamn Fordon. The customer has requested level 3 after a design change, revision D, where the seal got a new material. This is how the agent reads the PSW against the drawing, the dimensional report, IMDS and the customer's request:

PSW · 7714-210 · Rev D · Design change · Level 3 · IMDS 1048233/2 · 0.4120 kg
7714-210Part numberThe customer's number for the part✓ Same as in the customer's request
Rev DDrawing revisionRevision and date of the change✓ Same in dimensional report, control plan and PFMEA
Design changeSubmission reasonWhy the part is submitted✓ Matches the customer's change order
Level 3Submission levelPSW, sample parts and full documentation✓ The customer requests level 3
IMDS 1048233/2Material reportingThe substances in the part, reported in IMDS✗ Must apply to revision D, applies to revision C
0.4120 kgWeightMeasured weight, to four decimals✗ Must match IMDS, which states 0.3980 kg
Two of six fields do not agree, and both have the same cause: the IMDS report is based on the seal in revision C. The PSW is presented for signature only when they agree. Made-up data.
How every PPAP submission is checked

What is to be submitted is taken from the customer's requirements for the part: the level and the customer's CSR. Then the documents are checked against the drawing and against each other. Each row below is a separate check. The limits are AIAG's, unless the customer specifies others.

  1. 01
    The right documents for the levelWhich elements are submitted and which only have to be kept at your site depends on the level and the customer's CSR. The list is taken from the customer's requirements, not from a generic template.
    Level 3 · CSR
  2. 02
    The submission reasonThe reason in the PSW matches the change: new part, design change, changed material, new, refurbished or relocated tooling, tooling inactive for more than twelve months, new sub-supplier, changed process or new manufacturing site.
    Design change
  3. 03
    The same drawing revisionPSW, dimensional report, control plan, PFMEA and process flow diagram apply to the same revision, and it is the one the customer has requested.
    Rev D
  4. 04
    The dimensional reportEvery dimension and note on the ballooned drawing is in the report with a result within tolerance, for every tool, cavity or production line the customer requires.
    42 of 42 dimensions
  5. 05
    Special characteristicsCharacteristics the customer has marked as special are in the PFMEA and the control plan, with the customer's symbol.
    SC · CC
  6. 06
    The capability studyThe initial process study exists for the special characteristics. Ppk above 1.67 is accepted. Between 1.33 and 1.67 requires the customer's assessment. Below 1.33 is not accepted without a corrective action plan approved by the customer.
    Ppk 1.82
  7. 07
    Measurement system analysisThere is an analysis for the gauges the control plan refers to, for new and changed ones under AIAG and for all of them if the customer requires it. Gage R&R below 10 percent is accepted, between 10 and 30 percent depending on the application, above 30 percent not.
    GR&R 8 %
  8. 08
    Control plan, PFMEA and flow agreeThe same process steps in all three, and every special characteristic has a control and a reaction plan in the control plan.
    Op 30
  9. 09
    Tests and laboratoryMaterial and performance tests to the drawing's specifications are included with results. An external laboratory must be accredited to ISO/IEC 17025, or approved by the customer.
    ISO/IEC 17025
  10. 10
    Material data in the right orderThe sub-suppliers' data sheets are in IMDS before yours is sent, and yours is accepted before the PSW is submitted. If a link is missing it is requested at once.
    Seal → 7714 → PSW
  11. 11
    IMDSThe report has been sent to the customer, applies to the same revision and is accepted, and the ID is in the PSW. The substances are checked against GADSL and the customer's own lists.
    IMDS 1048233/2
  12. 12
    The weightThe weight in the PSW, in kilograms to four decimals, matches the weight in the IMDS report.
    0.4120 kg
  13. 13
    The sub-suppliersPurchased parts and materials have the sub-supplier's approved PSW, a valid IATF 16949 or ISO 9001 certificate, and ELV and REACH declarations and CMRT when the customer requires it. The sub-supplier's PPAP is reviewed by the agent the same way as your own, against your requirements, and whoever owns supplier quality at your company approves or rejects.
    PSW · CMRT
  14. 14
    The signatureThe PSW is signed by the person at your company appointed to do so. The agent fills in and checks, but never signs. Exceptions are stated in the explanation field, not left out.
    Signed
If everything agrees the PSW is presented for signature, and the package is submitted when it is signed. If something deviates the submission is stopped, and you get a question in Teams with the document and the customer's requirement side by side.

The checks are set up to your customers' requirements in the mapping, and new ones are added when the requirements change.

Your sub-suppliers' PPAP, the other way round

What you buy in must have the sub-supplier's own PPAP, and it has to be reviewed before your own can be submitted. The agent does it the same way: requests the package from the sub-supplier according to your requirements for the part, classifies what arrives, checks level, revision, certificates, dimensions and PSW against your requirements, and presents the result with every error marked. Whoever owns supplier quality at your company approves, rejects or requests supplementary documents in the web app, and the reply goes to the sub-supplier. At many suppliers this is the bigger pile, and the one reviewed entirely by hand today.

How IMDS is connected

IMDS may only be connected to other systems via IMDS Connect, DXC's licence for file exchange. Scripts, robots and AI that click in the IMDS web interface are not permitted under the IMDS terms of use, and the agent never does that.

  • You have IMDS Connect. The agent reads the daily download files with incoming data sheets, status and weight, and checks them against the PSW and the drawing revision. If a data sheet is to be sent, the agent prepares the XML file and a person at your company approves the upload.
  • You do not have IMDS Connect. The agent works outside IMDS. It requests material data from the sub-suppliers and reminds until it arrives, and shows you what needs to be done in IMDS. The check in IMDS is done by a person at your company.
  • The licence is yours. IMDS Connect is a company licence tied to your IMDS ID, priced by how many data sheets you upload and accept per year. If you already use a program that connects to IMDS you probably have the licence.
  • No real-time API. IMDS Connect is based on files, not on requests and responses. The check is made against the latest file, normally once a day.
Which route applies at your site we go through in the mapping.
Quality · PPAP
CF
The PPAP agent10:42
PPAP 2207 · Nordhamn Fordon AB
Submission on Thursday · Design change, revision D · PPAP level 3 · 10 documents
Ready
8 of 10, checked against drawing and customer requirements ✓
Deviates
The IMDS report for part 7714 is based on the sub-supplier's material data for the seal in revision C. The weight in IMDS, 0.3980 kg, therefore does not match the PSW, 0.4120 kg
The supplier
Material data in IMDS for the seal in revision D requested 22 September, reminded 26 September, no reply
The submission
Package prepared, submitted after your signature
Proposal
Submit the eight completed documents on Thursday and request interim approval, with IMDS as an open item. The customer is told today.
The customer granted interim approval with IMDS as an open item at the previous change of the same part.
Approve the proposalWaitChange
One click, and the agent notifies the customer and keeps reminding the sub-supplier. The package is submitted when the PSW is signed. Made-up data.

The agent takes the searching, the reminders and the uploading. You spend the time on what requires judgement: the deviation, the supplier that does not deliver its declarations, the customer with new requirements.

No new systems, no new logins. The agent logs in where you log in. Your quality system and your document archive stay as they are: the agent works in them and does not replace them. The connections to the suppliers' and customers' web portals are ours to build and keep running.

Do the maths

What the documentation costs you.

Move the sliders. The figures are calculated on your own numbers, not on an average.

The time
480
hours per year spent gathering, chasing and checking documents today
264 000 SEK
per year in working time
The default values are examples. Your own numbers, and how much of it the agent takes over, are established in the baseline measurement before implementation. A rejected submission costs two to three days of work, and a series delivery that waits costs more. We take that up in the walkthrough.
How we work

From the first conversation to operations.

  1. Walkthrough, 30 minutes. You tell us which customers require documentation, which documents it concerns and where they are today. We tell you what can be automated first.
  2. Mapping and baseline measurement. We go through real submissions with the person who gathers the documents today, write down the requirements per customer and measure the hours per submission before the agent is implemented. That becomes the yardstick for the result, and for what the agent pays back.
  3. Implementation and test. We start with a bounded part: the PPAP package for one customer or one part family. We implement the agent in your environment or in ours, together with your team, and test it against an answer key of your own submissions. Fixed price.
  4. Operations. We take application responsibility for the agent, always: a cost cap, a monthly report and a named person to call. If the agent runs in your environment, you operate the platform yourselves or through your IT partner, as today. If it runs in ours, we operate it.

What we need from you.

  • The person who gathers the documents today, a couple of hours during the mapping.
  • The customers' requirements: contracts, requirement lists or examples of packages you have sent.
  • Read and write access in your test environment, via API or login.
  • One hour with your IT, about your Microsoft or Google environment.
  • For the IMDS check: your IMDS Connect licence, or confirmation that IMDS is handled manually.
Key figures

This is what we measure.

  • The time — hours per submission, and hours per month in quality and engineering.
  • Submissions approved first time — share of submissions the customer approved without supplementary documents, the figure your customers already measure you on.
  • Submissions that were late — how many, and for how many days.
  • Missing and expired documents per sub-supplier — and how long the sub-supplier takes to respond.
  • Deviations stopped before submission — wrong revision, dimension out of tolerance, PSW and IMDS that do not match, caught before the customer saw it.
  • Time from change order to approved PSW — days, per customer.
  • Sub-suppliers' PPAP approved first time — share of incoming PPAPs approved without supplementary documents.
Common questions

This is what you usually ask.

  • What happens if the agent gets it wrong? The agent never approves on its own, and it never releases revisions in your PDM. It checks and shows what deviates, but it is always a person at your company who decides and signs the PSW before anything is submitted. If the agent misses something you see it before signing: the PSW is presented with every check and the document beside it, so you sign on what you see. The content, the risks in the PFMEA and the actions in the control plan, you review as today; the searching, the form checks and the reminders the agent does. Every step is logged.
  • Which documents does it cover? The ones your customers require: Part Submission Warrant (PSW) · Drawing and engineering change order · Dimensional and test results · Control plan, process FMEA and measurement system analyses · IMDS report · Sub-suppliers' PSW, IATF certificates and substance and conflict minerals declarations. Scanned documents are read in the same way as digital ones.
  • Does it read the content, or only check that the document exists? What is measurable, not the engineering judgement. The agent checks that the drawing revision is the same throughout the package, that the dimensions are within tolerance, that the operations in the flow, PFMEA and control plan agree and that the PSW and IMDS match, and it judges for itself what is wrong, with a reference to where in the document it is found. Whether the risks in the PFMEA are rated correctly, you judge, and the approval and the signature are always yours. A deviation comes to you before anything is submitted.
  • Do the suppliers have to change anything? No. The agent requests the documents by email or fetches them in the supplier's web portal, as you do today.
  • Does it work with our systems? With the systems you already have: the ERP, PDM, the quality system, the measuring room's files, email and Teams, and the sub-suppliers' and customers' web portals. Where there is no API the agent uses the web portal, as you do. IMDS only via your IMDS Connect.
  • Where does our data end up? The documents stay where you have them. The overview runs in our Azure in Sweden, or in your Microsoft environment if your IT requires it. The language model does not train on your data.
  • What does it cost? Your first customer through the agent: SEK 50,000, fixed price. Your systems connected and your first customer through the agent within two weeks of us getting access. Each additional customer: SEK 15,000. Operations and maintenance per month, counted on all your submissions: up to 3 per month SEK 6,000, 4–8 SEK 10,000, 9–20 SEK 16,000, above 20 by quotation. A submission is a PSW, resubmissions included, averaged per quarter. Month by month, 30 days' notice. A cost cap on the AI calls is included.
  • How long does it take? Your first customer goes through the agent within two weeks of us getting access to your systems. How many customers, part families and sub-suppliers are then added, and whether IMDS Connect is in place, sets the rest of the timeline, which you get after the mapping.
  • How long are we tied in? Not at all. Operations run month by month with 30 days' notice. The implementation is paid for once it is done, and what has been built in your environment is yours. If you cancel operations the agent stays with you, but without our monitoring and updates.
For your IT

How we implement and run it.

Show the technical overview
  • Identity. The agent runs as a service account in your Entra ID, with the least possible privileges per system. No admin accounts, no shared passwords.
  • Hosting. Runs in our Azure in Sweden by default, or in your Microsoft environment* if your IT requires it. The documents stay with you; the platform holds the overview, statuses and links. What leaves your environment is the calls to the language model, and they stay within the EU, see below.
  • Integration. API where the system has one: Microsoft Graph for email and Teams, and the native APIs of the ERP, PDM and quality system. IMDS is connected only via your IMDS Connect, never via the browser. Where there is only a web portal, at a sub-supplier or a customer, the agent drives the browser via Playwright, the same clicks you make.**
  • Document reading. Scanned and digital documents are read with text recognition in the environment the agent runs in. Every extracted value is saved with a reference to where in the document it is found.
  • Credentials. API keys and the service account's secrets are kept in Key Vault in the environment the agent runs in, as are the logins to web portals without an API. Never in a prompt, never in the code.
  • Decisions. The agent never approves on its own and never releases revisions in your PDM. Deviations arrive as a card in Teams with the document attached, and every submission is submitted only once a person at your company has signed the PSW. Who may approve a deviation is governed by rules you set yourselves.
  • Traceability. Every action is logged with account, time, part and submission. A locked copy of what was submitted is saved in your SharePoint, and the overview in the browser shows everything with your Microsoft login. Web portal steps are saved as screenshots.
  • The language model. OpenAI models in Microsoft Foundry, processed within the EU and never outside it, with data at rest in Sweden. What is sent is the text of the document and the requirements of the order, nothing more. Microsoft does not train on your data, and the retention of calls can be brought down to zero. If your IT requires it, the model runs under your own Azure subscription: then nothing leaves your tenant.
  • GDPR. The documents rarely contain personal data. Names, email addresses and phone numbers in the emails are replaced with placeholders before the call and restored in the response.
  • Application responsibility. Always lies with Cloudfox, from day one. We answer for the agent: new customer requirements, new document types, new suppliers. That it does the right thing and stops when it is unsure. That APIs are versioned, models are replaced and web portals are rebuilt. And what the AI calls cost, with a cost cap and alerts.
  • Platform responsibility. Covers the platform: tenant, accounts, network, updates, that the resources are up. If the agent runs in ours, which is the default, it lies with Cloudfox. If it runs in your environment it lies where operations lie today, with your IT department or operations partner.

* If you have Google instead of Microsoft the same setup applies: Google Workspace for email and chat, Google Cloud for hosting and keys.

** Web portals can have terms of use that restrict automation. We check the terms of every web portal in the mapping. Where automation is not allowed we use the system's interface or a manual step instead. IMDS, for example, may only be connected via IMDS Connect.

Book 30 minutes.

Tell us which documents your customers require and how you gather them today, and we will show you what can be automated first.

We use the details to reply to you. How we process personal data (in Swedish)

Your contact
Pontus Granborg
Medgrundare, Cloudfox

You talk directly to the person who implements the agent for you, from the first conversation to operations.

Email
pontus.granborg@cloudfox.se
Phone
+46 70 090 17 06
LinkedIn
linkedin.com/in/pontusgranborg